Re: Next problem, rpm organization

[Stephen Williams <steve@icarus.com>]

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.

greg@kroah.com said:
> As for the directory structure questions, I say just have a fxload
> subdirectory from the main root.  And move the Makefile that builds
> everything to the main directory also.

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