Re: architecture question

> =CE=A3=CF=84=CE=B9=CF=82 27/03/2012 07:24 =CE=BC=CE=BC, =CE=BF/=CE=B7 St=
=C3=A9phane Graber =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:
> vagrantc: I saw in irclogs that you were concerned about unwanted
> "ancestor" scripts, as I said we can override those with empty files.

not really what i was getting at...

this leaves no mechanism to override files with alternate packages. i.e. a
ltsp-custom-feature-addon package cannot override plugins of
ltsp-client-core, without rebuilding the ltsp-client-core package.

ltsp-build-client plugins support several layers where plugins can
override others. we didn't really have much room for this in the current
init-ltsp.d implementation either, though, so it doesn't matter too much.

> That still makes the changes more visible than having dozens of symlinks.

in general i agree, but i just wanted to raise that point.

live well,
  vagrant


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