[Scons-dev] Packaging logic?

[anatoly techtonik]

On Fri, Apr 3, 2015 at 7:28 PM, Kenny, Jason L <jason.l.kenny at intel.com>
wrote:

>  The current way is to get a source dist and install it.
>
> This would not stop. You would be able to do the same thing.
>

If nothing else will be broken then I don't mind against uploading wheels
to PyPI.


> The difference in the below would be:
>
>
>
> Pip install scons
>
>
>
> would be default go to the internet and get SCons
>

Ok.

pip install .
>
>
>
> would install the current setup.py in the directory ( and I should add
> allow you to then do a “pip uninstall scons” to remove it. You can still do
> a “python setup.py install” as well you however would now have meta
> generated to remove it with a nice command.
>

Not ok. SCons is a build system, so it should build itself to experiment on
a live code. If we can teach pip to invoke scons as a part of build step -
that is ok. I'd say that there is a even a demand for a cross-platform
build tool that can work with pip to build binary stuff like extensions.

-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150407/b0691f2c/attachment.html>