From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] udev spec file bits
Date: Fri, 17 Oct 2003 22:43:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106644308924845@msgid-missing> (raw)
On Fri, Oct 17, 2003 at 05:54:57PM -0400, Robert Love wrote:
> Hi, Greg.
>
> Some spec file changes. Primarily, this makes the thing build without a
> build root if so desired (i.e. build right out of /usr/src/redhat and
> the standard file system). It should still build from a build root,
> too.
>
> Also:
>
> - Add some Prereqs
> - Pass RPM_OPT_FLAGS to make so we build with the RPM build
> policy (i.e., optimizations, architecture, etc.)
> - Specify the exact files in %files to make sure we install
> everything properly and avoid a warning
>
> Patch is against udev-003
Thanks, I've applied this.
Hm, I would also like to add the /etc/hotplug.d/default/udev.hotplug
symlink, but rpm doesn't seem to like symlinks in the %files section.
Anyone know how to do this properly?
thanks,
greg k-h
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
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 reply other threads:[~2003-10-17 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 22:43 Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 21:54 [patch] udev spec file bits Robert Love
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-106644308924845@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.