On Mon, 24 Sep 2012, Wookey wrote:
Santiago, have you reached an opinion on whether you'd prefer to 1) split the gettext package into an MA:same libgettext-dev part and an MA:foreign gettext part (and change corresponding dependencies), or 2) mark it MA:allowed and change all the dependencies that only need the build-tool part to 'gettext:any' ?
I think splitting is probably the best option here, following Steve's advice: Steve Langasek wrote:
You could split the packages and put the issue to bed once and for all
The thing I don't like about the proposed patch is that it creates a single new package which is really the combination of two different -dev packages. So my plan would be to split it "the right way", by creating two additional packages: libasprintf-dev and libgettextpo-dev. We would then drop the "Provides:" in gettext, we would not have to add them anywhere, and it would be clear that those names are the right ones to be put in a build-depends. [ This is what I had in mind, but since we are in a freeze I had this issue postponed. Sorry for the late reply ]. Does this help? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
