All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload source organization
Date: Sat, 09 Jun 2001 16:35:14 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99210460222224@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99205388220304@msgid-missing>


david-b@pacbell.net said:
> subdirectories can work, I've worked with source trees like that.
> though methinks /sbin is wrong for any of these programs, they're not
> classic "single user mode binaries".

It's OK for the install to distribute sbin/ files to /sbin/ and /usr/sbin
on the target machine as is appropriate.

So here's another idea. Try this on for size:

I still create an admin/src/ directory and put under that directories
for compiled programs. These programs compile their binaries into
the admin/sbin directory, or admin/lib if it ever comes to that.
The install then would be able to find the things it installs in the
sbin/ and etc/ directories as now.

I think it is OK to have the src/ directory as an exception. This to
some degree mimics the layout on a target system anyhow, that would have
a /usr/src directory.


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

      parent reply	other threads:[~2001-06-09 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09  2:30 fxload source organization Stephen Williams
2001-06-09  2:48 ` David Brownell
2001-06-09  4:42 ` Stephen Williams
2001-06-09 16:35 ` Stephen Williams [this message]

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