On Sun, 22 Jul 2007, Frederik Holljen wrote: > On Thu, 28 Jun 2007 14:48:13 +0200, Kore Nordmann wrote: > > On Wed, 2007-06-27 at 16:51 +0200, Frederik Holljen wrote: > > > 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?
I'm for option 3 as well, but what Kore suggests here is going to be a pain in making the packages, as this doesn't follow any of the guidelines that we have. We should so something about the names of those script components though, like Tobias suggests. regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
