From: Aras Vaichas <arasv@magellan-technology.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] fix install/uninstall paths for cross compilation
Date: Thu, 27 Oct 2005 00:59:33 +0000 [thread overview]
Message-ID: <43602675.1050805@magellan-technology.com> (raw)
In-Reply-To: <435F163C.3080306@magellan-technology.com>
Kay Sievers wrote:
> On Wed, Oct 26, 2005 at 03:38:04PM +1000, Aras Vaichas wrote:
>
>>This patch fixes some problems with installing EXTRAS and uninstalling
>>binaries and man pages when DESTDIR has been set e.g. for cross
>>compilation, or creating an initrd
>
>
> Commandline options to make are automatically passed to the submakes,
> no need to list them explicitly.
Can you confirm this by echoing DESTDIR in, say, extras/run_directory/Makefile?
This gave me an empty string unless I explicitly passed it to the submake. Did
I make a mistake somewhere?
> DESTDIR is for packaging. What would a "uninstall" be good for?
To remove the man pages from an embedded Linux target which has no use for man
pages, or to remove an old version of udev from an nfsroot "live" filing
system. Considering that udev is in such active development, this will happen
frequently.
It's common for me to do something like "make install" and then follow with a
"make uninstall-man" or similar because it's easier during the development of a
package or live filing system.
But I understand your point - "why would one delete files from a package that
is to be shipped to somewhere else?" Yes?
Regardless, without my patch this Makefile was potentially fatal to the host
system. When I ran "make install", it installed the binaries and man pages to
the correct destination. e.g. /DESTDIR/sbin/ ... but when I ran "make
uninstall-bin" it deleted the binaries from /sbin !
"uninstall" should remove the files from where "install" put them.
regards,
Aras Vaichas
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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
next prev parent reply other threads:[~2005-10-27 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 5:38 [PATCH] fix install/uninstall paths for cross compilation Aras Vaichas
2005-10-26 14:57 ` Kay Sievers
2005-10-27 0:59 ` Aras Vaichas [this message]
2005-10-31 1:56 ` Kay Sievers
2005-10-31 4:08 ` Aras Vaichas
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=43602675.1050805@magellan-technology.com \
--to=arasv@magellan-technology.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).