Re: 1.6.0 problems with libguilereadline-v-12 and fix

[Robert Uhl <address@hidden>]

address@hidden (Paul Jarc) writes:
> 
> Here's one I like: <URL:http://cr.yp.to/slashpackage.html>.  This
> system puts each installation of each package in its own directory,
> so it's safe to install before testing.

The problem with that is it makes utter hell out of one's PATH--and
users don't get all apps by default.  Plus you get problems with tools
such as info and man expecting files in certain locations, so you get
to play with MANPATH (and INFOPATH, if there is such a thing).

I like how stow does it: everything goes in its own folder in
/usr/local/stow, and the stow command creates links from
/usr/local/bin, /usr/local/etc &c. to there.  It has some problems
with things like info's dir file--which is an index of all info
files--but a quick hack can fix that.  When you uninstall, you just
run stow -D, which deletes the links.  Then you may remove the
package's directory.

You can also use /usr/stow and get links in /usr/bin, /usr/etc,
/usr/share &c., or ~/stow or what-have-you.  It's a very flexible
tool.

Plus, it's generally as simple as:

    ./configure
    make
    sudo make install prefix=/usr/local/stow/PACKAGE_NAME

which is awfully nice.

> Adopting slashpackage means abandoning the FHS, but if Guile wants
> to convert in spite of that, I'd be thrilled.

I don't think that's a very good idea--the FHS is a nice thing, and
exists for a reason.

-- 
Robert Uhl <address@hidden>
Some people are born blind, others are born crippled, and some are born
Americans.  One should not be held responsible for what is essentially an
accident of birth.                                        --Harald Horgen