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

Re: Agenda for the 2009-05-26 Packaging Committee meeting



On 05/26/2009 11:34 PM, Richard W.M. Jones wrote:
On Tue, May 26, 2009 at 09:29:31PM +0000, Matej Cepl wrote:
Hans de Goede, Tue, 26 May 2009 13:15:23 +0200:
Can we please not remove the Group tag, it is actually quite usefull.
What we need to remove / loose is comps. Having all this info in a
centralized database is stupid. The spec files should tell which
group(s) the package belongs in. So that when one adds a new package,
this gets done right more or less automatically (and is part of the
review).
Hear, hear!!! And add Suggests:/Recommends: (which is the other part of
comps).

+1000
+1001 ...

I've just been involved with submitting a package for febootstrap to
Debian [yay, build Fedora images on Debian!], and I'm reminded yet
again what a good idea 'Suggests/Recommends' are.  I can Suggest
packages like 'filelight' for measuring the effects of image
minimization, without making it a proper dependency and consequently
pulling in the whole of KDE.

Rich.

soft-deps (Suggests/Recommends) is really hard to handle at the depsolver level. A depsolver need to now the hard ones, not stuff like 'it would look very nice to have pink bracelet to my little pony'. It is hard to make good decisions based on that, a asking the user every time is not a good solution IMO. You will need to take a popquiz every time you what to install a package. I can see that the information can be useful at a high level gui or in some kind of appstore. People there have bought 'foo' have also bought 'bar'. But at the lowlevel like rpm/yum is not very useful, because we don't have the needed infomation to make a good decision.

Tim


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