From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Next problem, rpm organization
Date: Mon, 11 Jun 2001 16:32:19 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99227719500757@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99210624825359@msgid-missing>
greg@kroah.com said:
> But the fxload isn't dependent on the hotplug-core, now is it?
Correct, and it will install even if hotplug-core isn't installed.
There is precedent for this relationship, for example the nfs-server
and nfs-clients packages, which are mutually independent, though from
the same source tree.
greg@kroah.com said:
> As for the directory structure questions, I say just have a fxload
> subdirectory from the main root. And move the Makefile that builds
> everything to the main directory also.
So I should create admin/fxload, and admin/Makefile, and encourage new
programs be added in directories under admin/<foo> and into the
admin/Makefile makefile. I can modify the spec file and install targets
apropriately.
I can do that, if you would like. My initial proposal was designed to
minimize the impact.
--
Steve Williams "The woods are lovely, dark and deep.
steve@icarus.com But I have promises to keep,
steve@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-06-11 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:03 Next problem, rpm organization Stephen Williams
2001-06-11 16:11 ` Greg KH
2001-06-11 16:32 ` Stephen Williams [this message]
2001-06-11 16:37 ` Greg KH
2001-06-11 17:05 ` David Brownell
2001-06-11 17:52 ` David Brownell
2001-06-11 17:52 ` Stephen Williams
2001-06-11 18:04 ` David Brownell
2001-06-11 18:22 ` Stephen Williams
2001-06-12 11:14 ` Thomas Sailer
2001-06-12 14:35 ` David Brownell
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-99227719500757@msgid-missing \
--to=steve@icarus.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).