From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Next problem, rpm organization
Date: Mon, 11 Jun 2001 17:05:31 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99228160616601@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99210624825359@msgid-missing>
> I'm thinking of rearranging the spec file to make these packages:
>
> hotplug-core
> hotplug-utils
>
> The -core package contains the existing scripts and makes up the directory
> structure on the target system. This includes the basic hotplug script
> and the rc files needed to enable the system.
Two packages, one being more or less the current hotplug package,
seems about right to me.
> The -utils package contains utility programs that specific devices
> might want or need. This is where the fxload program would go. Only
> packages that needed a utility program in here would depend on this
> package.
Where would you put stuff like "usbmodules", used for "cold-plugging"?
I guess I'm thinking that "fxload" is more like "usbutils", and maybe
what should happen is that the hotplug project should host that and
add "fxload" to it.
- Dave
_______________________________________________
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 17:05 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
2001-06-11 16:37 ` Greg KH
2001-06-11 17:05 ` David Brownell [this message]
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-99228160616601@msgid-missing \
--to=david-b@pacbell.net \
--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).