On Mon, 2015-01-26 at 13:41 +0000, Carnë Draug wrote: > Hi > > I have a set of configure tests which today I have copied and paste into > my 4th project. They are really simple and very general use-case [1], so > I am thinking of contributing them to SCons. They check for LaTeX document > class, package, availability of a program, and perl modules. At least the > last two have counterparts on autoconf. > > Can I contribute them to SCons? I am aware of the SCons autoconf recipes > wiki page [2] but that's far from ideal. I wonder if the existence of such > page means that such recipes are not desired on SCons. > > If not, is there any sort of SCons extras? autoconf has at least the > autoconf-archive [3].
We are trying to build up a culture of people using DVCS (usually Git or Mercurial) to provide "rolling release" versions of tools and other extras. Wiki pages are good for many things, but storing software is not one of them. Many of the pages of the SCons wiki are there more for historical record than ongoing usefulness. So if you can structure you extra as a tool or general package and then publicize the repository, it can get added to the various publicized lists. If then people start saying "this should be in the distribution", that can initiate a process leading to the tool/package being absorbed into the main distribution. The classic examples are the bits and pieces on this page: http://www.scons.org/wiki/ToolsIndex -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
