On 02/25/2013 07:09 PM, Tim Landscheidt wrote:
This may be overkill for some libraries, and you can emulate the package management provided by the OS with a bunch of ad-hoc scripts and very strict SOPs, but in a environment where all boxes will run Ubuntu and knowledge about Debian packaging is relatively widespread, I think going the extra mile (well, rather yard) is definitely worth it.
That's an interesting approach. Something along the lines of a "Tool Labs PPD" then that relies on puppet for deployment?
There are clear upsides, there, but I see two hurdles that need to be considered:
1) what of tools that want or need to use different versions of the same asset; and 2) who gets to update that package (i.e. who decides when to pull and build)?
The alternative, storing the shared code in gerrit, means that the individual tools simply clone "locally" and can merge or cherry-pick as needed.
I don't think it's clear at this point in time which is the better model, honestly.
-- Marc _______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
