On 06/25/2013 01:58 PM, Jakub Wilk wrote: >>> Why does it need such a new version of coreutils? (This, on the >>> other hand, might be something worth explaining in the >>> changelog.) This build-dependency makes the package unbuildable >>> on i386, which is stuck with an earlier version of coreutils. >> I changed the dependency to coreutils from stable (>= 8.13-3.3). >> >>> Also, why does it need such a new version of bash? > > Well, you didn't answer my questions. :)
How can I determine the correct version? Can I test it under oldstable and make a dependency on its versions if the package works? >>> Why priority "extra"? I'd use "optional". > >> From the Debian Policy: ... I checked the practice in existing >> packages and I'm a little bit confused. For example the packages >> python-nose (test discoverer and runner) and libmysqlclient-dev >> are optional while python-mox (mock object framework) is extra. >> >> What's the rule here? I thought that you don't want to install >> development tools unless you have specialized (i.e. programming) >> needs. > > To give you some numbers: 27% of all binary packages have priority > extra. 22% of binary packages in section devel have priority > extra. > > And I bet that most of these are because "extra" used to be > dh_make's default, not because of deliberate maintainers' > decisions. > OK, so I'll change to "optional". BTW: what kind of packages should be classified as "extra"? Thank you for help! Regards -- Grzegorz Niewisiewicz -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ca15b4.9020...@niewisiewicz.pl
