Sunday, 2. March 2008, Richard Freeman Ви написали: > George Shapovalov wrote: > > The good thing about this approach is that it only requires an initial > > investment of organizing and automating things but does not add any > > regular work to the devs. In fact, if the "tested" category becomes > > popular enough, it can cut the work for stable testers, may be even by > > something like a factor of 10 eventually (due to less requests for > > explicit stabilizaion being issued).. > > We might also aim to make it easy for users to mix-and-match levels of > stability by package. I know it is possible already, but perhaps it > could be improved, or pre-canned lists of packages that users might > typically want bleeding-edge vs stable could be compiled. Well, we already have "system set" and it is defined in profile. With users being able to define and use their own profiles all that is left to do is to add an ability by portage to use different stability settings for system and out-of-system packages, as the most trivial approach. Of course more complex combinations are possible, but would require a proper discussion.
> I think there are a large number of users who wouldn't mind less > stability on packages that won't prevent booting or network-access or > general use of their system. If some nice-to-have utility breaks I > don't mind reverting it, but if baselayout goes haywire I could spend > hours just getting my system to boot. Exactly. I did not mention this in order not to overcomplicate my previous message, but this is one of the things I had in ming for a long time. Besides > I like your idea though. Thanks! Although it is somewhat strange to hear "idea" when it has been an "old news" :) (at least for me), just check the timing of that bug I mentioned above. I merely adapted one of the not-yet-implemented issues discussed there to the present situation. Oh, btw, these two issues (extra stability levels and separate stability rankings for groups of packages) are independant enough to make it possible to implement them separately. George -- [email protected] mailing list
