unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Release now?
Date: Thu, 27 Feb 2003 12:45:10 -0600	[thread overview]
Message-ID: <878yw1mukp.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <rmid6ld1tte.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "27 Feb 2003 13:07:09 -0500")

Greg Troxel <gdt@ir.bbn.com> writes:

> There is a large transition question, though - guile 1.6 already has
> libraries in a particular place.  For 1.8 to have a new place is
> probably fine, but this would be disruptive to those who have already
> found a satisfactory solution.  Hence my notion of having the
> version-named midfix be optional, so Debian can use it and NetBSD can
> keep using separate prefixes.

Though at least for end-users compiling using guile-config, I'd hope
the transition would be rather painless.

> Also, we might consider having a different prefix rather than a
> 'midfix', which seems awkward.  With /usr/lib/guile/1.4, guile/1.4
> gets appended to $(libdir).  The alternative of /usr/guile/1.4/lib,
> where prefix is /usr/guile/1.4 instead of /usr, seems cleaner to me.

I don't really think that's feasible, at least not as the default.  At
least for most of the linux distributions (and I'd guess solaris,
etc.) that would be in contravention of the FHS (and predecessors),
and I would guess also the LSB.

> Summarizing:
>
>   If the installed locations of guile 1.6 changes, I object because it
>   will cause work for people who have already coped.

Hmm, but I'm only talking about changing the location of one file (a
symlink) on the lib side, per library, i.e. libguile.so, which would
affect packagers, but shouldn't affect anyone using guile-config.

Also we're going to *have* to change the install location of the
headers, i.e. /usr/include/guile/VERSION/, at least for normal
autoconf style installs, i.e. FHS compliant installs since using
/usr/include/libguile.h doesn't allow multiple dev versions to be
installed.

>   I prefer the different prefix rather than a midfix.  A configure
>   option to add a midfix seems ok, but given that we already have
>   --prefix, it seems like more work.

I don't really think this is likely to be acceptable as a default.  If
you've ever seen the mass objections from *many* unix camps to
attempts to violate the FHS-style /usr/lib/*, /usr/include/* approach,
you know what I mean.  I can understand -- there are good reasons for
many of the choices made in the FHS.

That doesn't mean we shouldn't have a way to support other
approaches.  In gnucash we had --enable-opt-style-install.  I don't
think I'd want to name the option that now, but it arranged for things
to be /etc/gnucash/blarg by default, but to be able to be
/opt/gnucash/etc/blarg when requested.  It was somewhat a pain to
arrange and maintain, but it can be done.

>   If the default behavior includes either midfixes or extra symlinks,
>   I object, because it is imposing what some may view as uncleanliness
>   on everyone because some decline to use -R.

I think we may just have to agree to disagree here.  From the user's
perspective, the -L approach should be transparent, and from anyone
else's perspective, it should be trivial to either support a
--configure option that changes that default, or just let them "mv
guilelibdir/* libdir/" in whatever build/install script/infrastructure
they're using.  Or we could possibly have an option.

If what you're arguing for is in fact an "opt-style" install, then
that's fine, but I think it'll have to be something that can be
enabled rather than the default since it's my impression that FHS
style layouts are the definite majority.

>   Differing prefixes and a ./configure option to symlink into another
>   prefix is a clean solution

I think maybe I still don't have a good impression of what you're
preferred solution is (and that's likely my fault) -- I'm not sure
what the "prefixes" are here.

Overall, I still feel like the changes I've proposed are a fairly
small alteration to the current strategy, and seem to be likely to
work everywhere.  That's what's driving my immediate inclination.

And although we may want to do it anyway, having more than one
strategy, especially if they're significantly different, does increase
the support burden both on the coding side, and on the end-user side.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-02-27 18:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 12:37 Release now? Mikael Djurfeldt
2003-02-24 13:08 ` Dale P. Smith
2003-02-24 13:21   ` Mikael Djurfeldt
2003-02-24 13:32 ` Greg Troxel
2003-02-25 13:34   ` Marius Vollmer
2003-02-25 16:08     ` Greg Troxel
2003-02-25 18:38       ` Rob Browning
2003-02-26  1:51         ` Greg Troxel
2003-02-26  2:27           ` Rob Browning
2003-02-27 14:25             ` Greg Troxel
2003-02-27 15:21               ` pkg-config support for guile Greg Troxel
2003-03-22 23:31                 ` Marius Vollmer
2003-04-23 21:22                   ` Greg Troxel
2003-05-16 23:21                     ` Marius Vollmer
2003-02-27 16:54               ` Release now? Rob Browning
2003-02-27 18:07                 ` Greg Troxel
2003-02-27 18:45                   ` Rob Browning [this message]
2003-02-27 19:25                     ` Greg Troxel
2003-02-27 20:14                       ` Rob Browning
2003-02-27 19:06                 ` Rob Browning
2003-02-27 19:13                   ` Rob Browning
2003-02-27 19:36                     ` Greg Troxel
2003-02-27 20:02                       ` Rob Browning
2003-02-27 20:54                         ` Greg Troxel
2003-02-27 21:07                           ` Dale P. Smith
2003-02-27 21:30                             ` Dale P. Smith
2003-02-27 21:47                           ` Rob Browning
2003-04-25 19:26                           ` Neil Jerram
2003-02-25 16:28     ` Andreas Rottmann
2003-02-24 18:35 ` Rob Browning
2003-02-25 13:20 ` Marius Vollmer
2003-03-03 14:06   ` Mikael Djurfeldt
2003-04-25 19:28   ` Neil Jerram
2003-04-25 22:59     ` Marius Vollmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878yw1mukp.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).