Re: Bug#550860: ITP: gnaughty -- downloader for adult content
Patrick Matthäi <email@example.com> writes:
> Philipp Kern schrieb:
>> On 2009-10-14, Russ Allbery <firstname.lastname@example.org> wrote:
>>> Yeah, it's a bit of a marginal case. We have, for instance, Perl
>>> modules to talk to the Amazon APIs in main, although in most of those
>>> cases the API is relatively open and some other sites also implement
>> The appearance of Eucalyptus is pretty recent, though. So you'd need
>> to wait until a free service of an API gets released? How feature
>> complete does it need to be? If I release a "compliant" porn directory
>> with only one pic, would that be appropriate? And I could easily make
>> it non-porn too.
I suspect that the right thing to say is that if the API can be
implemented in free software, the software can go into main, but it's
really hard to figure out how to draw the line with installer packages.
Probably drawing the line between code and data is worthwhile. If the
package needs to download and install non-free code on the system to run,
it's probably contrib. If it's just a tool for manipulating data, which
may be non-free, then main is a reasonable place to put it.
>> zsnes used to be in contrib, but somebody made the case that there
>> could be, in fact, free roms, because the way how to program the box is
>> not exactly secret anymore. (If they would be buildable on Debian is
>> another question.) It lives in main now and my gut feeling is that
>> it's the right thing to do, given that the code base is free to modify,
>> share and gives you the usual rights of a free software license (here:
The ROM thing is a case of the code issue, and is probably more
complicated than programs that deal only with data.
I think, regardless, given the information on this thread, there's no
reason why this program would need to be in contrib.
> Please move this whole discussion to debian-legal now.
No. debian-legal is the place for license nit-picking, which isn't what
this discussion is about.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>