[Scons-users] [Scons-dev] .scons/

[Bill Deegan]

There's not going to be a 2.6

3.0 is next, likely a beta in a week or so.

And we're unlikely to change from site_scons.
We have a documented deprecation cycle, but most importantly, this is the
first request from any user for such a change.

Also, this discussion would be better brought to the users mailing list
since it's not about developing the tool, but more about using and usage of
the tool  so I'm cc'ing that list.
Please move future responses there.

-Bill


On Sun, May 21, 2017 at 11:05 AM, anatoly techtonik <techtonik at gmail.com>
wrote:

> On Sun, May 21, 2017 at 4:33 PM, Russel Winder <russel at winder.org.uk>
> wrote:
> > On Sun, 2017-05-21 at 15:18 +0300, anatoly techtonik wrote:
> >> I am thinking about introducing project level .scons/
> >> directory located in the same directory as top level
> >> SConstruct.
> >
> > I believe there is already a per project capability using the same
> > naming as for per person. So:
> >
> > <project-base>/site_scons/site_tools
>
> Yes. There is. However, the convention is awkward. I'd deprecate it
> for something more up to date with modern standard. And those
> standards say that configuration for various development helpers
> is better kept separated by prefixing it with dotted name.
>
> Another reason is that "tools" concept is not intuitive, because
> SCons tools usually wrap real tools and that creates confusion. It
> is better if plugins wrap tools.
> --
> anatoly t.
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170521/1c8e8e61/attachment.html>