Re: [gentoo-user] Another reason to begin USE with -*
On Monday 13 March 2006 05:53, Roy Wright wrote: Boyd Stephen Smith Jr. wrote: Plus, it's /completely/ trivial to add -* to your USE or (using the great euse tool) euse -D useflag. Or, for those type A personalities out there, tweak your /etc/portage/package.use. Another tool is ufed (use flag editor). Nicely combines flag name, set state, and brief description. From this thread, I realized I hadn't ever reviewed my use flags, just added ones as needed for the past 1.5 years. So added the -* to start with. A few surprises like tetek. Found a half dozen deprecated flags. Then using ufed I discovered several new flags to try. This has me wondering if there is a utility to help manage the use flags. I'd like to know: * Which use flags I have set that are not used by anything I have installed. * Which use flags are deprecated. * Which use flags are new. Ideally I'd just add this to my daily.cron job. Thank you, Roy Instead of ufed I'd recommend profuse, it has the same options as ufed and more. Really a great tool, very easy to use and gives you a clear list of what use flags you have enabled (I do prefer the ncurses profuse -n command above gtk) -- Rick van Hattem Rick.van.Hattem(at)Fawo.nl pgpHf498Q7BMq.pgp Description: PGP signature
Re: [gentoo-user] Another reason to begin USE with -*
Michael Stewart (vericgar) wrote: Roy Wright wrote: This has me wondering if there is a utility to help manage the use flags. I'd like to know: * Which use flags I have set that are not used by anything I have installed. * Which use flags are deprecated. * Which use flags are new. If you are using a recent portage, you can use the --newuse flag, which will show which USE flags have changed. I'm guessing you are referring to emerge --newuse. That just selects packages where a use flag for an ebuild is different from the last time the package was built. I'm more interested in discovering brand new use flags. Say some package, foo, creates a new use flag, bar, then I'd like to see something like: New Use Flags: bar (used in: foo) It also would be nice to see when particular package changes the set of available use flags between versions. Changed USE flag sets in the following packages: foo-1.0.0 (a b c) foo-1.0.1 (a c d e) Thank you, Roy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
On Monday 13 March 2006 03:21, Roy Wright [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] Another reason to begin USE with -*': I'm more interested in discovering brand new use flags. Say some package, foo, creates a new use flag, bar, then I'd like to see something like: New Use Flags: bar (used in: foo) Save use.local.desc and use.desc before each sync and diff with the new version after. It also would be nice to see when particular package changes the set of available use flags between versions. The -pv output of emerge shows this. A flag that was not available in your current version but it available in the one you are installing, will be colored yellow and postfixed with '%'. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
Boyd Stephen Smith Jr. wrote: The -pv output of emerge shows this. A flag that was not available in your current version but it available in the one you are installing, will be colored yellow and postfixed with '%'. Great. So something like the following in my cron.daily/portage.update script should do the job: echo Save old use.desc rm -f /usr/portage/profiles/use.desc.old cp /usr/portage/profiles/use.desc /usr/portage/profiles/use.desc.old echo Save old use.local.desc rm -f /usr/portage/profiles/use.local.desc.old cp /usr/portage/profiles/use.local.desc /usr/portage/profiles/use.local.desc.old echo Syncing portage tree... emerge --sync 2 /var/log/portage.cron.log /dev/null status=$? if [ $status -ne 0 ]; then echo Portage sync failed, exiting update. exit $status fi echo Changed use flags: diff /usr/portage/profiles/use.desc.old /usr/portage/profiles/use.desc diff /usr/portage/profiles/use.local.desc.old /usr/portage/profiles/use.local.desc echo Running eupdatedb... eupdatedb --quiet --nocolor 2 /dev/null echo Running update-eix... update-eix --quiet echo Checking for updates... rm -f /tmp/emerge.output /usr/local/sbin/einfo --update --deep --newuse world emerge --update --deep --pretend --verbose --nospinner --newuse world /tmp/emerge.output emerge --update --deep --fetchonly --quiet --nospinner --newuse world /tmp/emerge.output cat /tmp/emerge.output echo New USE flags indicated by trailing percent sign in: grep -P \S+% /tmp/emerge.output Thank you, Roy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
On Monday 13 March 2006 15:13, Roy Wright [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] Another reason to begin USE with -*': Boyd Stephen Smith Jr. wrote: The -pv output of emerge shows this. A flag that was not available in your current version but it available in the one you are installing, will be colored yellow and postfixed with '%'. Great. So something like the following in my cron.daily/portage.update script should do the job: Looks good, with the following caveat: cp /usr/portage/profiles/use.desc /usr/portage/profiles/use.desc.old cp /usr/portage/profiles/use.local.desc /usr/portage/profiles/use.local.desc.old emerge --sync 2 /var/log/portage.cron.log /dev/null The last line will delete the .old files you just created when it syncs /usr/portage/profiles. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
Boyd Stephen Smith Jr. wrote: The last line will delete the .old files you just created when it syncs /usr/portage/profiles. Nice catch! Thank you. Changed the directory for the old files to /var/portage/profiles. That should be safe. echo Save old use.desc mkdir -p /var/portage/profiles rm -f /var/portage/profiles/use.desc.old cp /usr/portage/profiles/use.desc /var/portage/profiles/use.desc.old Thank you, Roy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
On Sat, 11 Mar 2006 19:20:31 -0500 Walter Dnes [EMAIL PROTECTED] wrote: | Why in (diety's) name does the the average user need apache2? Or | emboss (European Molecular Biology Open Software Suite)? Uh, USE flags are not packages. You're misunderstanding how USE flags work. Adding apache2 and emboss to the default USE flags does not mean that users will get Apache or Emboss. Having these USE flags in the defaults is entirely sensible and correct, and provides expected behaviour for the majority of users. Anyone claiming otherwise simply doesn't understand what's going on. -- Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) Mail: ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm signature.asc Description: PGP signature
Re: [gentoo-user] Another reason to begin USE with -*
On Sunday 12 March 2006 11:51, Ciaran McCreesh [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] Another reason to begin USE with -*': On Sat, 11 Mar 2006 19:20:31 -0500 Walter Dnes [EMAIL PROTECTED] wrote: | Why in (diety's) name does the the average user need apache2? Or | emboss (European Molecular Biology Open Software Suite)? Uh, USE flags are not packages. You're misunderstanding how USE flags work. Adding apache2 and emboss to the default USE flags does not mean that users will get Apache or Emboss. Having these USE flags in the defaults is entirely sensible and correct, and provides expected behaviour for the majority of users. Anyone claiming otherwise simply doesn't understand what's going on. Amen. Plus, it's /completely/ trivial to add -* to your USE or (using the great euse tool) euse -D useflag. Or, for those type A personalities out there, tweak your /etc/portage/package.use. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
Boyd Stephen Smith Jr. wrote: Plus, it's /completely/ trivial to add -* to your USE or (using the great euse tool) euse -D useflag. Or, for those type A personalities out there, tweak your /etc/portage/package.use. Another tool is ufed (use flag editor). Nicely combines flag name, set state, and brief description. From this thread, I realized I hadn't ever reviewed my use flags, just added ones as needed for the past 1.5 years. So added the -* to start with. A few surprises like tetek. Found a half dozen deprecated flags. Then using ufed I discovered several new flags to try. This has me wondering if there is a utility to help manage the use flags. I'd like to know: * Which use flags I have set that are not used by anything I have installed. * Which use flags are deprecated. * Which use flags are new. Ideally I'd just add this to my daily.cron job. Thank you, Roy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
Roy Wright wrote: This has me wondering if there is a utility to help manage the use flags. I'd like to know: * Which use flags I have set that are not used by anything I have installed. * Which use flags are deprecated. * Which use flags are new. Ideally I'd just add this to my daily.cron job. Thank you, Roy If you are using a recent portage, you can use the --newuse flag, which will show which USE flags have changed. -- Michael Stewart [EMAIL PROTECTED] Gentoo Developerhttp://dev.gentoo.org/~vericgar GnuPG Key ID 0x08614788 available on http://pgp.mit.edu -- signature.asc Description: OpenPGP digital signature
[gentoo-user] Another reason to begin USE with -*
On Sat, Mar 11, 2006 at 06:31:14PM +0300, Andrew Gaydenko wrote Thanks! It helped. 2006.0 default USE list has 'apache2' flag on, and 'subversion' package has this USE flag. I wouldn't have believed it if I hadn't seen it with my own eyes. There it is in... /usr/portage/profiles/default-linux/x86/2006.0/make.defaults USE=alsa apache2 apm arts avi cups eds emboss encode esd foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mp3 mpeg nptl ogg opengl oss pdflib png qt quicktime sdl spell truetype udev vorbis X xml xmms xv Why in (diety's) name does the the average user need apache2? Or emboss (European Molecular Biology Open Software Suite)? After the ipv6 fiasco, I began USE with -*, like so... USE=-* 3dnow X a52 aac alsa bzip2 cdr dga dio divx4linux dri dvd dvdr dvdread encode exif ffmpeg flac fortran gb gif gtk2 imlib jpeg maildir mikmod mime mmap mmx mng mp3 mpeg ncurses nptl nptlonly nsplugin offensive ogg opengl plotutils png posix quicktime readline sdl sharedmem slang sockets sse theora threads tiff truetype vcd vorbis win32codecs wmf xpm xv zlib I feel that my decision was correct. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
Walter Dnes wrote: Why in (diety's) name does the the average user need apache2? Or emboss (European Molecular Biology Open Software Suite)? After the ipv6 fiasco, I began USE with -*, like so... http://thread.gmane.org/gmane.linux.gentoo.user/143049 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Another reason to begin USE with -*
On Sat, Mar 11, 2006 at 04:58:57PM -0800, Ryan Tandy wrote Walter Dnes wrote: Why in (diety's) name does the the average user need apache2? Or emboss (European Molecular Biology Open Software Suite)? After the ipv6 fiasco, I began USE with -*, like so... http://thread.gmane.org/gmane.linux.gentoo.user/143049 I know; I was in on that thread. As another participant pointed out, fetchmail has long delays when compiled with ipv6 support, on an ipv4-only machine. Probably it does an ipv6 lookup, waits for the timeout, then falls back to ipv4. Since I use fetchmail, that is more than a hypothetical consideration for me. The whole point behind -* is to prevent future surprises. Yesterday it was emboss and ipv6. Today it's apache2. What's next; and when? One reason I'm using Gentoo is because I want the maximum control over my machine that's possible without going to LFS. Starting USE with -* is part of my strategy for maintaining control. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
