Greetings, SCons has always been (as much as possible) a batteries include tool. For me personally, and also from many questions on the mailing list and IRC, having mainstream tools not in the core confuses users. I consider QT to be a mainstream tool..
I'd suggest the following: 1) deprecate qt, rename it qt3 2) integrate qt4 and qt5 into the core. Thoughts? I know I'm disagreeing with others, hopefully this isn't just bike sheding (Please call me on it if it is). That said, I think it would be a great idea to add non-mainstream tools as python packages distributed via pypi which would install into the core or in such a way that the core would find them. -Bill On Sun, Apr 14, 2013 at 3:50 PM, Dirk Bächle <[email protected]> wrote: > On 15.04.2013 00:09, Gary Oberbrunner wrote: > >> Dirk makes a very good point, one we've thought about for a long time. >> It might be a good time, as we prep for the next version, to think about a >> contrib system. (In any case, we should either import the Qt4/5 tools or >> delete the Qt3 one though.) Dirk, is there a way for us to leverage pypi >> for this? Can it install tools into a dir that we could add to the >> site_tools path for instance? I don't know if we could (or should) build a >> web-based contrib system ourselves. >> >> > I don't want to install the contributed tools into the usual site_scons > directory. They go straight into the SCons install, alongside with "doc", > "src", "QMTest" there would then be a "contrib" folder. > I can't offer any experience with pypi, so I don't know whether this is > possible...but something like this should be the goal. > > We can't be the first people on the planet trying to distribute additional > software packages...there has to be a solution out there. Let's find and > use it, instead of inventing our own. ;) > > > I am trying to get started on toolchain revamp ideas (which would >> integrate with the above idea). I'll try to put out some kind of strawman >> document soon. >> >> > Sounds great! > > Dirk > > > ______________________________**_________________ > Scons-dev mailing list > [email protected] > http://two.pairlist.net/**mailman/listinfo/scons-dev<http://two.pairlist.net/mailman/listinfo/scons-dev> >
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
