linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: Next problem, rpm organization
Date: Sat, 09 Jun 2001 17:03:59 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99210624825359@msgid-missing> (raw)


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.

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.

-- 
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

             reply	other threads:[~2001-06-09 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09 17:03 Stephen Williams [this message]
2001-06-11 16:11 ` Next problem, rpm organization Greg KH
2001-06-11 16:32 ` Stephen Williams
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-99210624825359@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).