On Thu, 30 Apr 2009, Guillem Jover wrote: > Another option could be to add a new modifier, like P(rivate) or > U(ser), to be used like XPBS-Field: which would preserve the X-. But > then you need a new enough dpkg-dev to be able to get that field.
I like that idea. It's not a big deal to have to use a recent dpkg-dev, there aren't so many users of custom fields... > I like (XB-)Private-, it works now, and it's pretty clear about what > it means. If it's going to be used only for internal use, then Private- > should be enough, but if those packages are going to be made public and > used by other distros or derivatives, it might make sense to namespace > them with project or company name to avoid possible collisions, due to > more chances of uncoordination about those additions, so something like > XB-Private-Distro-Field (I guess the same should apply if those > projects or companies add support to their dpkg for those fields, > though, like in Distro-Field). It's a bit too verbose for me but I could live with that. :) Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
