On Thu, Nov 7, 2013 at 6:30 AM, Carsten Haitzler <ras...@rasterman.com> wrote:
> On Tue, 5 Nov 2013 12:09:42 -0200 "Eduardo Lima (Etrunko)" <ebl...@gmail.com>
> said:
>
>> (Note, I'm replying to e-devel only, on purpose)
>>
>> Now that you're in the release mood too, what about organizing the
>> release folder a bit? Just take a look at the directory listing:
>>
>> http://download.enlightenment.org/releases/
>>
>> We could keep to the minor level, such as E 0.18, EFL 1.8 and don't
>> include the micro version (0.18.0 and 1.8.0, and so on). Something
>> like this:
>>
>> releases/
>>   - enlightenment/
>>     - 0.18/
>>     - 0.19/
>>   - efl/
>>     - 1.8/
>>     - 1.9/
>>   - terminology/
>>
>> I am proposing this for the upcoming releases, I wouldn't change the
>> current state so we make sure we won't break any scripting that might
>> be used by distros.
>>
>> Regards, Etrunko
>
> is there a reason for this? i always just expected to fill releases with
> tarballs and have web pages/wikis/news releases point to the tarballs to use
> for that release...
>
> is it that you want to use a wget script or something?
>

To be honest, I was not thinking about wget but you came with very
good use case. Anyway, I would rather type the download.e.o url
instead of digg around a wiki or blog to find the links for the
packages. In the end just a matter of personal preference.

-- 
Eduardo de Barros Lima ◤✠◢
ebl...@gmail.com

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to