Re: architecture question

hi,
On Sat, 24 Mar 2012 10:46:20 +0100
Wim Muskee <[email protected]> wrote:

> Something similar is already implemented for init-ltsp, where the
> distro specific functions end up in /client/init-ltsp.d/$distro
> The distro specific functions can be packaged in
> /usr/share/ltsp/init-ltsp.d/* by first copying
> /client/init-ltsp.d/common and adding /client/init-ltsp.d/$distro.
> 
hmm, do you really want to ship all functions for all possible
distros ? that seems like a waste of space. our initial plan with the
plugins was that you actually only install the plugins your distro uses
at package build time. while it may be nice to have a configdir.d
approach for a distro that builds everything ad-hoc from source
like gentoo does, for a binary distro this means that you either ship
plugins/functions for all the distros you dont want in your package or
you dont do this but then you have quite some maintenance effort to
do to selectively put in only the bits your distro uses.

ciao
	oli

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk9tnhIACgkQSsOT+6LQaTbLsQCfaOn9UFqiFZs1hGqYWk5P9jAJ
nukAn1pXvNfvVI9Q1BlcrN/dcJqkH6z1
=H+jZ
-----END PGP SIGNATURE-----