In <[🔎] 5da0588e0906060734w602f6cb7y9e1736ac2eb54dc@mail.gmail.com>, Rince wrote: >On Thu, May 28, 2009 at 4:55 PM, Piotr Ożarowski <piotr@debian.org> wrote: >> * shold not be a native package > >The package this is updating is a non-native package only in name - it's a >native package with a .diff attached to update the version from 1.2 to > 1.3. I don't think you are clear on native vs. non-native. It has a specific technical meaning in Debian packaging. It is not simply "specifically for Debian" or the opposite of "converted from an RPM" or even "developed on Debian infrastructure for use by Debian users". A native package has a version number that does not contain a hyphen. A native source package is only two parts: the .tar.gz and the .dsc. A non- native package has a version number that does contain a hyphen; the part after the first hyphen is the "packaging (sub)version". A non-native source package is in three parts: the .tar.gz, the .diff.gz, and the .dsc. When deciding to package something as native vs. non-native, you should generally go non-native. It allows packaging-only issues to be fixed without updating the .tar.gz, which reduces the load on the mirror network. Native packaging should only be used when the Debian packaging cannot be logically separated from the main body of source or when the package could not reasonably be useful on a non-Debian system. (The latter is closer to policy, but the former is probably better practice.) In particular, Debian, a DD, a DM, or any of the Debian packaging teams could be "upstream" and it still might not be correct to have the package be native. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.