> > 3. Make a new component just for the script > > + Nice handling of requirements > > - Lots of components > > I personally like this variant most. Perhaps we can make those > components available as single components in the pear installer, but > aggregate them in one single directory in trunk, so that we would end up > with something like: > > trunk/ > - component a > - component b > - scripts/ > - component a > - component b > > This would enable us to maintain a reletively clean directory structure > and also have a clean dependency structure, or would that hurt our > release master to hard? :) > > Anothewr possibility would be to prefic all components created like this > with "script", to be able to easily distinguish between them and the > real components. Derick, comments on this?
Cheers, Frederik -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
