[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Info about non-free ITP



Hi,
I've just finished coding a middleware (written in C++) to operate Italian ID smartcards (CIE), and I've been asked to prepare a deb package. The code contains a source file that, for security reasons, should not be published, so I've a couple of questions in mind:

- should I consider the entire middleware non-free and provide a binary only deb package or it could be advisable to separate the free and non-free code in, respectively, a source upstream tarball that should be published and a binary blob containing only the (small) non-free part? In this latter case, is the resulting package considered eligible for main section or is it still non-free?

- in the ITP, is there a particular string to be written as 'license' for the non-free case?

Many thanks in advance,
Andrea della Porta

Reply to: