On Thu, Nov 10, 2011 at 11:08 PM, Linus Arver <linusarver@gmail.com> wrote:
But I think that the PKGBUILD prototypes are meant to be a very simple, sane starting point for devs/contributors to create their own. If we end up introducing too many concepts into these prototypes, maybe they may not be helpful in the end. Perhaps there should be two sets of prototypes --- an "beginner" and "advanced" version. Or maybe the ideas you introduced in your email belong to the Arch Wiki, and not the prototype (under a heading like "Advanced Git PKGBUILD Techniques).
i think the best route is some kind of lower level integration, at makepkg (or ?) level ... i know someone brought up a bug report regarding just that. i'll mull that a bit and probably make noise there instead :-)
I think you should make very small, incremental changes at a time. That way, you won't scare off all the people on the list who are not as technically competent in git as yourself. ;)
indeed :-) i'll seek the appropriate channel for these changes.
P.S. When writing a list of paragraphs, use '*' or '-', not ')'.
bah! i've done that for quite some time :-) i use `)` specifically because: 1) a) ... looks nice and clear to me, but i tend to skip backfilling the letter/numbers. maybe `*)` or `x)` is better? i'll consider `*`, but `-` is ... nay :-) aaaanyways, i'll look into lower level integration so users can simply set a variable or something, and not even call git directly. -- C Anthony