Greg Troxel <[EMAIL PROTECTED]> writes:
> The mechanism I'm proposing is a bit more flexible than that, but the
> basic idea in both cases is that the core distribution (either Emacs
> or Guile) has a view on where it wants add-on packages to be installed
> (and hence which may be differen
Greg Troxel <[EMAIL PROTECTED]> writes:
> I meant that when a guile-using package does 'make install', it can
> hook itself into the already-installed guile. Guile can and certainly
> should create config.scm in the build tree before install. Then,
> regardless of whether a binary package of som
before deciding about tags and descriptions, I think we need to be
clearer on the semantics of these directories and why they'd be used.
Let me take a stab at it, and I'm sure I'll leave out other's use
cases.
$(guileprefix)/share/guile
top-level place within guile's prefix. currently has sl
The mechanism I'm proposing is a bit more flexible than that, but the
basic idea in both cases is that the core distribution (either Emacs
or Guile) has a view on where it wants add-on packages to be installed
(and hence which may be different from the add-on package's $prefix).
I think th
Neil Jerram <[EMAIL PROTECTED]> writes:
> Greg Troxel <[EMAIL PROTECTED]> writes:
>
> > I was trying to contort the tag mechanism into doing what you showed
> > how to do earlier. Now I realize there's no need, so with the caveat
> > that I'd like the docs to explain how to do in-own-prefix inst
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Neil, I also fully support your proposal.
Thanks.
>> ((load-path
>> local
> ^
>
> I'd make this `local-1.6' by default, assuming that modules that may
> flawlessly run on any Guile version are an exception rather than the
> rule
Yes, agree
Greg Troxel <[EMAIL PROTECTED]> writes:
> I was trying to contort the tag mechanism into doing what you showed
> how to do earlier. Now I realize there's no need, so with the caveat
> that I'd like the docs to explain how to do in-own-prefix installs as
> you did in email, I can fully support you
Andreas Rottmann <[EMAIL PROTECTED]> writes:
> I strongly support making this the default/standard way, too. I'd be
> highly annoyed (well, that's an understatement ;)) if a "./configure
> && make && sudo make install" of some package would put files under
> /usr just because guile happens to be i
