Re: architecture question

Στις 24/03/2012 11:46 πμ, ο/η Wim Muskee έγραψε:
> Several decisions to be made:
> generic options, followed by examples between ()
>
> * the name of the function extension dir
>   - $command.d/$distro (init-ltsp.d/Gentoo)
>   - $command-functions.d/$distro (ltsp-update-image-functions.d/Ubuntu)
>
> * the name of the extension functions file
>   - $command-functions-$distro (ltsp-info-functions-debian)

I think the command itself can contain the functions, e.g.:
ltsp-info:
   server_packages() {
     die "Your distro needs to implement this function"
   }
   client_packages()
   ...
   . /usr/share/ltsp/client-common-functions
   main code

client-common-functions is a renamed copy of ltsp-common-functions, to 
allow for installing ltsp-server alongside ltsp-client (LP #950945).

Then client-common-functions would source
   /usr/share/ltsp/$(basename $0)-functions,
if it exists, so in this particular case, it would source
   /usr/share/ltsp/ltsp-info-functions.

That script would vary by distro, so its trunk name would be e.g.
Debian-functions.d/ltsp-info-functions, or any of the others that Wim 
suggested.


I can do the trunk changes for that too, if distro maintainers agree.

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