Re: fxload source organization

[Stephen Williams <steve@icarus.com>]

david-b@pacbell.net said:
> 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.

Except that each individual program is rarely a single C source file.
gflashd (er, fxload) is two source files, a readme and a makefile,
and it will surely grow as various kitchen sinks get added. I really
doubt you want all that piled into a flat sbin directory.

OK, so it's a good thing I asked. How 'bout create under the sbin
directory a directory for each compiled program, whereas scripts can
be edited in place as files as they are now. For example, I can make
admin/sbin/fxload as a directory and populate it with the source and
makefile for fxload. Then I can add into the root makefile the needed
fiddly details to cause that to be compiled.

The spec file can be made smart enough to do the install of the
compiled binaries in the subdirectory. Will this jive with the debian
way of doing things?


david-b@pacbell.net said:
> Or add a "make install" target to the makefile. 

Good idea. I can tackle that as well once these other issues are
dealt with.
-- 
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