linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] DESTDIR for udev
Date: Wed, 29 Oct 2003 22:32:59 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106746713522346@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106735713126878@msgid-missing>

On Wed, Oct 29, 2003 at 11:30:27PM +0100, Adrien Beau wrote:
> On Wednesday 29 October 2003 20:28, Greg KH wrote:
> > 
> > > > The hotplug symlink looks bogus. DESTDIR is for packaging,
> > > > not for --prefix.
> >
> > Are these names documented as the default somewhere in the LSB
> > or something like it?  What's wrong with using prefix in the
> > rpm file?
> 
> I haven't looked at udev, but generally speaking, --prefix is
> used to specify where on the filesystem the software will *live*,
> while DESTDIR is used to specify under which "root" directory the
> files will be put during a make install.
> 
> The key difference is that the --prefix will sometimes be
> compiled somewhere into the software (as an hardcoded default
> path to a config file or data directory, for example) while the
> DESTDIR has no influence on the software.
> 
> Typically, --prefix is specified at ./configure time, and is
> either /usr or /usr/local (usual default), while DESTDIR is only
> specified at make install time, and can have any value useful to
> the "make install"er.
> 
> I don't know if there is any proper documentation or standard for
> these features. Both come with almost every software that uses
> automake/autoconf as part of its build system.

Ah, thanks for the explaination.  As udev isn't using automake/autoconf
(and I don't want it too, either, please don't send patches doing
that...) I had to try to remember what the defaults were :)

I've accepted the DESTDIR patch.

thanks again.

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2003-10-29 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 16:04 [PATCH] DESTDIR for udev Olaf Hering
2003-10-29  1:52 ` Greg KH
2003-10-29  6:54 ` Olaf Hering
2003-10-29 11:56 ` Olaf Hering
2003-10-29 19:28 ` Greg KH
2003-10-29 20:03 ` Olaf Hering
2003-10-29 22:27 ` Greg KH
2003-10-29 22:30 ` Adrien Beau
2003-10-29 22:32 ` Greg KH [this message]

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=marc-linux-hotplug-106746713522346@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).