Re: [As-users] 2.2.2 Release Announcement!

Jeff Krebs (
Fri, 2 Jun 2006 22:25:14 -0500

You can install the AS files anywhere you want with PREFIX
and "make install" will put them where required. Or you can
install by hand, if you follow the configure. I agree that
the AS configure is nice, but it's rather absoulute when
creating paths in the config files.

The original post was about things not showing in the
menus.  To me that means "paths", and that means that
something was deviated from, probably after "make install".
Might have been renaming a directory, or perhaps inadvertently
copying a directory to the wrong location.

I got the impression that the user was trying to have something
along the lines of /usr/local/afterstep-2.2.2 with the AS files
and dirs in it (wharf, desktop/, applications/, etc.).  That
won't occur with the PREFIX set as it was.

I only run one version of AS at a time, system-wide.  If I were
to play with multiple versions, I'd probably do as you are
recommending.  For a one-at-a-time approach, my recommendation
would be a PREFIX of /usr or /usr/local and letting configure
and install take their course.  For folks running multiple
AS versions, this topic is probably un-needed.

I could be wrong.  It happened once before :). Might happen

Jeff Krebs

* John Gruenenfelder ( wrote:
> On Fri, Jun 02, 2006 at 08:24:13AM -0500, Jeff Krebs wrote:
> >You need to look at the --prefix configuration again...
> >
> >Setting it to /usr/local/afterstep-2.2.2 is incorrect.  Open
> >the "configure" file in the AS tarball and do a search for
> >"--prefix".  Everything builds on this descriptor.
> >
> <snip>
> >
> >I see what you're tring to do, but you can't do it that way
> >with just PREFIX.  At a minimum, you need to change:
> >
> <snip>
> >
> >Jeff Krebs
> You sure about that?  I think he's doing it correctly.  This is how I test out
> CVS copies of AfterStep.  I don't want to clobber or remove the Debian AS
> packages, so I install my AS into its own little area, typically:
> --prefix=$HOME/bin/asinstall
> The AS config system is very nice in this regard.  The default configuration
> files are adjusted when you build to use the path you specify.  When I want to
> use my CVS AfterStep I only need to do three things:
> 1) Change my .xsession to load $HOME/bin/asinstall/usr/bin/afterstep instead
> of just 'afterstep' which is the system default copy.
> 2) Change the ModulePath line in $HOME/.afterstep/base to point to the new
> location.  I keep both lines in the file and then just comment out the one I
> don't need.  The other lines in 'base' will still point to the system default
> locations, but since those are for pixmaps and icons it really doesn't matter.
> 3) Add $HOME/bin/asinstall/usr/bin to the front of my PATH so it takes
> precedence over the old copy.  Unless you need some of the other AS supplied
> programs like ascommand, you can actually skip this step.  Setting ModulePath
> is all you need for AS to be able to find the modules.
> Now, this isn't as simply as just running afterstep-2.2.2, for example, but
> it's still a very easy sequence of changes to make.
> -- 
> --John Gruenenfelder    Research Assistant, UMass Amherst student
>                         Systems Manager, MKS Imaging Technology, LLC.
> Try Weasel Reader for PalmOS  --
> "This is the most fun I've had without being drenched in the blood
> of my enemies!"
>         --Sam of Sam & Max
As-users mailing list