public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: Mike Frysinger <vapier@gentoo.org>, Nathan Scott <nscott@aconex.com>
Subject: library placement
Date: Tue, 30 Dec 2008 07:26:26 -0500	[thread overview]
Message-ID: <20081230122626.GA14350@infradead.org> (raw)


There's a three year old patch from Mike in bugzilla that stops
symlimking the libaries into two different directories if they
are in fact not actually different:

	http://oss.sgi.com/bugzilla/show_bug.cgi?id=430

After reviewing it again I don't see the point of having two copies
names for them.

The .so libraries should go into PKG_LIB_DIR (aka /lib in Debian) because
need them at runtime, potentially from tools outside of /usr.  The .a
and .la libraries are purely development ones and should go into
PKG_DEVLIB_DIR (aka /usr/lib in Debian) as we won't ever need them
while running programs.

Given that we're currently working on the xfsprogs 3.0.0 major release
this might be the time to make this change.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2008-12-30 12:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=20081230122626.GA14350@infradead.org \
    --to=hch@infradead.org \
    --cc=nscott@aconex.com \
    --cc=vapier@gentoo.org \
    --cc=xfs@oss.sgi.com \
    /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