From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Sat, 09 Jun 2001 02:48:51 +0000 Subject: Re: fxload source organization Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > 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