All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Next problem, rpm organization
Date: Mon, 11 Jun 2001 16:37:55 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99227769202300@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99210624825359@msgid-missing>

On Mon, Jun 11, 2001 at 09:32:19AM -0700, Stephen Williams wrote:
> 
> 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.

True, ok, I'm convinced :)


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

I like this, and don't mind moving things around a bit if it makes
sense.  If David agrees I say do it.

thanks,

greg k-h

_______________________________________________
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

  parent reply	other threads:[~2001-06-11 16:37 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 [this message]
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-99227769202300@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.