On Tue, 2002-02-05 at 03:18, Sam Ruby wrote: > Josh Lucas wrote: > > > > ok, one more time answering myself. I figured out why the cvs element > > wasn't showing up. It's because it is now a child of the module element > > as opposed to the project element. > > Sorry about that. This is based on a suggestion from Jason. > > If you are watching vindico, Scott is moving it back. (perhaps only > temporarily) > > My feeling at the moment is that Jason is right. Independent of how the > code is implemented, modules come from places (like cvs) and contain > projects. Projects are either installed or contain build instructions.
I think it does belong in the parent of project/package/whatever. It can help keep things seperate. > > To make things clearer, I've also been tempted to have different names for > things which are installed (<package> perhaps) from things which are built > (<project>). Then we can build a set of parallel definitions for every > project... installed vs built, and people can construct their profiles > and/or workspaces based on their choice. > > > I was also thinking of two possible adjustments to the script element. > > Why 'force' a project to have a .sh script? Perhaps we could drop that > > hard-coding in the bash.xsl file so any type of script could be used. > > I only use this in one case... bootstrapping ant. In the ant cvs there are > two files "bootstrap.sh" and "bootstrap.bat". Since I build on both > platforms, the project definition says > > <script name="bootstrap"/> > > And the bash.xsl and win2k.xsl add the appropriate suffix. > > Suggestions? Hmm.. I didn't see that. I don't want to overload the element but perhaps an attribute flag saying whether the 'default' extension should be used. I'll play with it a bit. > > > Also, what about having another attribute which would allow for > > arguments to be passed to the script in a similar way that a target can > > be passed to ant. > > Cool. > > > I adjusted my copy of Gump to do both of these in order for it to work > > here and all was well. I can send you the simple patch if you'd like. > > Patches are always welcome! > of course! I'll rework it and send it off. thanks, josh -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
