Tomek Lutelmowski wrote: > I think these two features would be very nice for server enviroments: > > 1. For stability reasons, relaying only on "x86" flag is often not > sufficient. There are many > cases when someone masked package as stable, then, few hours later (after > users feedback) its > reverted to "~x86". After syncinc portage tree, I never know which packages > marked as stable are > truly stable and well tested by community. My idea is to include new flag for > emerge. For examle: > # emerge -pu --stablesince=48h world Would list all packages for upgrade, > which has not been > changed since 48 hours, so there is low possiblity that this list includes > untested packages.
Sounds logical to have this feature. It might simplify life. Otherwise, a wrapper script should be able to do the same task. But what about security bugfixes then? Always waiting 48h is not good, so you'll end up using glsa-check after `emerge -pu --stablesince=48h world` or something. Or was there an option (or suggestion for such) to emerge to update all packages that are security related? > 2. In all my server instalations, I like to keep portage tree as small as > possible - for two > reasons: syncinc speed and disk space ussage. Now I can only use > RSYNC_EXCLUDEFROM flag in > make.conf to exclude portage branches from syncinc. Much more convinient and > efficent would be > RSYNC_INLCUDEFROM flag, so I could define which branches of tree I want to > sync. The portage tree > will be much smaller, and I wouldnt have to remove new branches that I dont > need to sync. Of > course in longer term such flag would help to lower bandwich usage of rsync > servers. What about going the Apache way: RSYNC_ORDER="INCLUDE,EXCLUDE" RSYNC_INCLUDE="foo" RSYNC_EXCLUDE="bar" That will work in all cases and altgough a bit more difficult to implement, works in all situations, as a "standasd" way to represent such situation, and easy to understang for the novice (is it?). > What do you think about such features? Although this is server related, shouldn't it be going to portage devs as well? I think one of them are reading this ML. Kalin. -- |[ ~~~~~~~~~~~~~~~~~~~~~~ ]| +-> http://ThinRope.net/ <-+ |[ ______________________ ]| -- [email protected] mailing list
