architecture question
Wim Muskee <[email protected]> Sat, 24 Mar 2012 10:46:20 +0100
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <CAKzfqkfvfRFRfjz-C14C9j4YD7vX4yH2dH1YX-yMsEdQ6bh7ww@mail.gmail.com> |
hi all,
There has been some talk about taking a more function (instead of
plugin) based approach to deal with distro specific issues in
executing the various LTSP commands.
The main difference is that in each case, the common functions are
sourced first, after which the distro specific one(s) are sourced,
overlaying common function which need a distro specific solution.
An example of this is the already implemented ltsp-vendor-functions,
which is sourced at the end of ltsp-common-functions. Each distro is
able to package it's own ltsp-vendor-functions.
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.
My question to you all is this:
When moving to this architecture, how should the upstream trunk store
this information and how should it be packaged?
This information would end up in the developer notes as well,
providing distro implementers with some clear guidelines.
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)
* the collection dir (in which dir these extension dirs and files end up)
- /server|client/plugins (/server/plugins/ltsp-build-client.d)
- /server|client/extensions (/client/extensions/ltsp_config.d)
- /server|client/functions (/client/functions/ltsp-info-functions.d)
- /server|client/ (/client/init-ltsp.d)
* the packaging of the function extension dir contents
- /usr/share/ltsp/$extension_dir (/usr/share/init-ltsp.d)
- /usr/share/ltsp/$collection_dir/$extension_dir
(/usr/share/ltsp/plugins/ltsp-build-client.d)
* the packaging of the extension functions
- /usr/share/ltsp/$command-functions
(/usr/share/ltsp/ltsp-update-image-functions)
- /usr/share/ltsp/$collection_dir/$command-functions
(/usr/share/ltsp/extensions/ltsp-update-image-functions)
------------------------------------------------------------------------------
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