[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GMG-Devel] ./configure && make now mandatory
From: |
Berker Peksağ |
Subject: |
Re: [GMG-Devel] ./configure && make now mandatory |
Date: |
Mon, 23 Feb 2015 00:45:09 +0200 |
On Mon, Feb 23, 2015 at 12:40 AM, Christopher Allan Webber
<address@hidden> wrote:
> Boris Bobrov writes:
>
>> On Sunday 22 February 2015 23:50:57 Christopher Allan Webber wrote:
>>> Hello all,
>>>
>>> As part of the upcoming release, a number of changes have happened. We
>>> no longer do insane things like commit .mo files into the repo or
>>> minified javascript and the like (or we do a lot less of the latter, and
>>> are working towards even less of it). As such, we need some way to
>>> "build" these steps.
>>>
>>> This process has been rolled into one step:
>>>
>>> ./bootstrap.sh && ./configure && make
>>> [...]
>>
>> How do I do setup.py develop now?
>
> setup.py develop still works, it's just that the ./configure && make
> makes the initial thing for you.
>
> I'm getting the sense that "making the virtualenv for users by default"
> might not be making sense :)
I think it's a good idea. Many users are not familiar to the Python
ecosystem and deployment best practices. Perhaps we can add a warning
or a y/n step to the "make" command.
--Berker