Re: architecture question

Στις 24/03/2012 12:12 μμ, ο/η Oliver Grawert έγραψε:
> hmm, do you really want to ship all functions for all possible
> distros ?

The packaging code would take care to include only the required files.

E.g. in trunk we'd have:
init-ltsp.d/common/*   # common plugins
init-ltsp.d/Debian/*   # debian plugins
init-ltsp.d/Ubuntu/*   # ubuntu plugins
init-ltsp.d/Gentoo/*   # gentoo plugins

Then debian/ltsp-client-core.install would contain the following:
init-ltsp.d/common/*   init-ltsp.d/
init-ltsp.d/Debian/*   init-ltsp.d/
init-ltsp.d/Ubuntu/*   init-ltsp.d/

...so that only those files would be shipped, and the Ubuntu plugins 
would overwrite the Debian plugins, and those in turn would overwrite 
the common plugins.

It's like HTML cascading style sheets, each plugin "below" in the 
hierarchy overrides the ones above it. And empty files can be used if 
some common/ or Debian/ plugins aren't needed in Ubuntu.
The result is cleaner I believe, no need for a whole load of symlinks in 
trunk.


Actually, stgraber can we do that for Precise? It'll save us path 
incompatibilities problems in the next versions...
I'll remove the symlinks from trunk and change a couple of lines in the 
initramfs scripts, if you agree to do that small packaging change in the 
next upload.

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net