On Thu, 21 Feb 2008 11:04:21 -0800 [EMAIL PROTECTED] wrote: > On Thu, Feb 21, 2008 at 07:44:49PM +0100, Jes?s Guerrero wrote: > > > Well, I made an ebuild for .23 and .24 long ago, though no one seems to care > > about fvwm users for quite a long time :P > > > > http://bugs.gentoo.org/show_bug.cgi?id=191638 > > > > You can also use the live-ebuild in the devnull overlay (use layman for > > that). > > Both ebuilds are mine and have been around for a long time. In fvwm, > > usually, > > the latest version (even cvs) is usually more stable than any previous one. > > > > Fancy stuff is rarely committed, so, almost all commits are bugfixes, > > and that 's why it can only get more and more stable. If you have some > > problem > > with any of these ebuilds, just ask. Though they have been tested for a long > > time and should work painlessly. > > I've not yet used overlays or layman; can I beg for a quick summary > for dummies? :-) Unfortunately, I am away from that machine for the > next week or so, and won't be able to report success or not until I > get access to it again. > The quick picture is "emerge layman". Then you just need to edit your make.conf and add this at the end of the file. Be sure you put it at the end so it doesn't get overwritten by accident.
======cut here========= source /usr/portage/local/layman/make.conf =====/cut here========= Then update the list of overlays with layman -f. You can now list the overlays with layman -L, the installed ones with -l, and you can add a new one with layman -a <overlay>. For example, to get the devnull overlay, you would do "layman -a devnull". >From now on, you just need to run "emerge -pv fvwm" and you should see that fvwm is going to be updated to 9999, which means that is a live ebuild (based on cvs, svn, git or whatever). Make sure you update your layman list regularly with -f, and that you sync the installed overlays with "layman -S". To delete overlays that you will no longer use, you can use -d. > Back when I ran slackware, there were some packages which I always > updated immediately because they were always good code: fvwm and > postgresql were among them. I know postgresql lags some, which is > annoying, but I had no idea fvwm was so out of date. Should I add a > requtes to that bug for moving it into the main ebuilds, or is there a > better way of requesting that? You can add another petition at the end of that thread like many people already did if you want... I don't know if it is worth it, though. :( -- Jesús Guerrero <[EMAIL PROTECTED]> -- [email protected] mailing list
