On 11/21/2012 10:11 PM, Luis Felipe Strano Moraes wrote:
> On Wed, Nov 21, 2012 at 9:36 AM, Gustavo Sverzut Barbieri
> <barbi...@profusion.mobi> wrote:
>> On Wed, Nov 21, 2012 at 8:35 AM, Carsten Haitzler 
>> <ras...@rasterman.com>wrote:
>>
>>> On Wed, 21 Nov 2012 08:21:53 -0200 Gustavo Sverzut Barbieri
>>> <barbi...@profusion.mobi> said:
>>>
>>>> This is bad. Either do 1.7.2 before next alpha, or at least 1.7.2-alpha1
>>>>
>>>> We really want people to test with the exactly same software. That's the
>>>> way to avoid problems like this one, it should never ever happened at
>>> this
>>>> point!
>>>>
>>>> Wasn't discomfitor running from stable EFL to avoid these issues?
>>> he's runing from the 1.7 branch - which is what will be 1.7.2... but that
>>> didnt have the fix until i added it today. the alpha shouldnt have passed
>>> "make
>>> distcheck".
>>>
>>
>> running from the branch isn't enough. he must run from the last release
>> tarball to be sure he has exactly the same as other users. If there need to
>> be a fix in EFL before next alpha, he must firstly release new EFL snapshot
>> or release, then get E17 on top of that.
>>
>> this is the only way to assure users will be able to compile. I'm being
>> picky here because we're at alpha4 already, very close to end and these
>> kind of things were not expected to happen. But you know, the default theme
>> is far from complete and thus the development may introduce some
>> breakages... then I recommend you, the theme maker, to also run the same
>> setup.
>>
>> as for make distcheck, I have no idea... likely he did not run it? How is
>> the alpha release procedure going on? Just make distcheck and it's gold?
>> Asking more folks at #edevelop to give it a try to tarballs before doing
>> the announcement? Testing with some pristine VM running standard distros
>> (fedora and ubunut)?
> I'm testing (post-release) the alphas on a pristine vm just to make
> sure that the packages install ok and have no issues. Could help mike
> with doing this pre-release as well.
>
> But I agree, having to ask users to patch by themselves edje (or run
> from the svn branch) is not a really good idea.
>
> Best regards,
> --lf
>
>

I am doing similar for openSUSE on a clean vm updating, deleting .e 
running first time, checking connman then having a quick play around, I 
am also running alphas on a old laptop

>>
>>
>>
>> --
>> Gustavo Sverzut Barbieri
>> http://profusion.mobi embedded systems
>> --------------------------------------
>> MSN: barbi...@gmail.com
>> Skype: gsbarbieri
>> Mobile: +55 (19) 9225-2202
>> ------------------------------------------------------------------------------
>> Monitor your physical, virtual and cloud infrastructure from a single
>> web console. Get in-depth insight into apps, servers, databases, vmware,
>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>> Pricing starts from $795 for 25 servers or applications!
>> http://p.sf.net/sfu/zoho_dev2dev_nov
>> _______________________________________________
>> enlightenment-devel mailing list
>> enlightenment-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
>


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to