From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload source organization
Date: Sat, 09 Jun 2001 02:48:51 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99205507321835@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99205388220304@msgid-missing>
> My inclination here is to create under admin/ the src/ directory
> and put fxload under that. I can make a Makefile in the src/ directory
> that builds all the directories, and a Makefile in fxload that builds
> the fxload program. This should work out well enough as all compiled
> programs can be put under src/.
Well, I chose "admin" originally for administrative scripts,
with etc/ and sbin/ directories to match the conventional
installation points.
The admin/debian subtree doesn't quite fit in with that
scheme, nor does the manpage that's at the top level
rather than living in usr/man/man8 (and hmm, fxload
should get one of those too).
Still, I unless we create a new organization for things
that need to be compiled, I'd like to see locations of
the compiled programs match conventional install
points. So for example maybe usr/sbin/fxload.c (and
usbmodules.c, pcimodules.c) would make more sense.
> I predict that the next puzzle will be how to organize the install
> process. So far, it looks like a bunch of copies and hand-made
> directories, unless you are using the .spec file. Should I stick with
> that and update the .spec file appropriately?
Or add a "make install" target to the makefile.
- 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-09 2:48 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 [this message]
2001-06-09 4:42 ` Stephen Williams
2001-06-09 16:35 ` Stephen Williams
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-99205507321835@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).