Excerpts from Peter FELECAN's message of Fri Jul 31 10:20:23 -0400 2009: > Yeah, when all the methods, procedures and tools involved in our > processes are documented it'll be reasonable to ask. Until then, you are > free to look in my home directory on the build stack, where everything > is open.
Ok, that's a fair point against not using GAR, but you could still pop your stuff into the legacy part of the svn tree... Documentation is a weak point, and I've really not contributed much in that regard. There should be enough info to get started with 'out there' but part of the problem right now is that it's scattered around somewhat. If you're willing to learn, though, I'll help you move some packages into GAR...offer valid for as long as you want it to be. Any maintainers interested in getting started with GAR can _always_ feel free to ping me directly. > I know recipes for RPM's, DEB's, &c. What's a recipe from the point of > view of gar? Can you show me one? It's the same really. You're defining 'special' variables, providing custom bits of scripts (when necessary) in the appropriate places and learning the appropriate Make targets. RPM defined it's own domain specific language for this...GAR is a language built on top of functionality offered by (GNU) Make. It's very flexible, allowing you to interject code at pretty much any place you need to (and for most builds, some you don't!). HTH -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
