On Tue, 4 Sep 2012 16:11:14 -0600, Sebastian Kuzminsky wrote: > On Sep 4, 2012, at 15:46 , Kent A. Reed wrote: >> Presumably because it introduces a new dependency on an external >> project >> https://libcpuid.svn.sourceforge.net >> >> I'm not sure what the right answer is here. Putting this >> experimental >> driver into master makes it easily accessible to folks like me who >> forget Michael's git hub but at the same time it's what the Saturday >> Night show would call Not Ready For Prime Time. > > I generally dislike forking external projects and including a copy of > them within LinuxCNC. It adds the developer burden of merging from > the external project, and bloats our repo and our packages. > > I'd prefer to use external packages that are available as debian > packages for our supported distros (LTSes Hardy, Lucid, and Precise), > or (if that's not possible) packaging the external project as a deb > and making it available in our debian archives (like Jeff did with > asciidoc to make it available on Hardy). > > It just makes for more modular, debuggable, sharable software over > all.
One of the things that I have seen done time or two, is to place a stable/canonical version in the source tree, and then build off of an external one if it is available. Other than that, I agree to have complete copies of all external dependencies. It is a bloody PITA to have someone pull the plug on some critical package, then you can no longer properly support your product. Need an example? Look no further than RT-Linux... ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
