On 19/01/14 13:14, David Seikel wrote:
> On Sun, 19 Jan 2014 11:52:55 +0000 Chris Michael
> <[email protected]> wrote:
>
>> On 19/01/14 11:23, David Seikel wrote:
>>> On Sun, 19 Jan 2014 20:40:47 +1030 Simon <[email protected]> wrote:
>>>
>>>> On 01/19/2014 04:13 AM, David Seikel wrote:
>>>>> On Sun, 19 Jan 2014 00:26:45 +0900 Cedric BAIL
>>>>> <[email protected]> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> On Sat, Jan 18, 2014 at 11:08 PM, Stefan Schmidt
>>>>>> <[email protected]> wrote:
>>>>>>> On Fri, 2014-01-17 at 11:08, Daniel Kolesa wrote:
>>>>>>>> quaker pushed a commit to branch master.
>>>>>>>>
>>>>>>>> http://git.enlightenment.org/core/efl.git/commit/?id=6db16915951af61d28f62f4de7c14c76e4303f18
>>>>>>>>
>>>>>>>> commit 6db16915951af61d28f62f4de7c14c76e4303f18
>>>>>>>> Author: Daniel Kolesa <[email protected]>
>>>>>>>> Date:   Fri Jan 17 19:07:59 2014 +0000
>>>>>>>>
>>>>>>>>        edje: use luajit by default, if you want lua use
>>>>>>>> --enable-lua-old
>>>>>>> I'm unhappy with this commit.
>>>>>>>
>>>>>>> Where and when was it decided to switch on a new default
>>>>>>> dependency? For instance jenkins is broken for all efl related
>>>>>>> builds now because nobody told me or beber in advance that
>>>>>>> luajit will be needed from now on. And as I have a busy weekend
>>>>>>> I will only be anle to look into this from Monday. I think
>>>>>>> something like this should be communicated before the actual
>>>>>>> change hits the repo.
>>>>>> I second you on that. The fact that the bot got broken is
>>>>>> something really bad and we should avoid that. Beber and Stefan
>>>>>> are doing a great job at mainting it and are very responsive. It
>>>>>> is good practice to at least talk with them before.
>>>>> Switching to LuaJIT 2.0 was planned, but I thought I was going to
>>>>> do that a bit later.  After some discussion where I present my
>>>>> results.  I also would have mentioned the Ubuntu PPA this old
>>>>> dinosaur uses for the more recent LuaJIT
>>>>> https://launchpad.net/~mwild1/+archive/ppa coz Ubuntu LTS only has
>>>>> an old beta of that version.  I've not found one for Debian
>>>>> dinosaurs, or other distros.  I can't recall off the top of my
>>>>> head what distro/version our jenkins is running on, so I can't
>>>>> suggest how to install the right LuaJIT version.
>>>>>
>>>>> I agree with the part about the white space changes should have
>>>>> been a separate commit, though that discussion should be a
>>>>> separate email thread.  B-)
>>>>>
>>>> luajit is the second dep not available in the main openSUSE repo
>>>> (bullet was the first), fortunately i can pull it from the games
>>>> development repo, but if we don't have it i'm guessing most other
>>>> distro's don't have it yet.
>>>
>>
>> Then you/they can not use luaJit (--enable-lua-old)
>>
>>> LuaJIT 2.0.0 was released in November 2012.  So the current Ubuntu
>>> LTS (12.04) predates that and could only have a beta version.  So
>>> does the Ubuntu release after that (12.10).  The two latest non LTS
>>> Ubuntu versions have the released version (13.04 and 13.10).  The
>>> next Ubuntu LTS is due out in three or four months.  For those that
>>> don't know, Ubuntu uses a year.month format for their version
>>> numbers, and do a release every six months, you do the math.
>>>
>>> Likely other distros have the full 2.0.0 release, it's only long
>>> tern stable distros like Ubuntu LTS that might have trouble.  I've
>>> not checked, but Debian stable might also have trouble.  Naturally
>>> other distro versions older than one year are likely to not have
>>> the 2.0.0 release.  Doesn't take long to became a dinosaur around
>>> here.  Roar! B-)
>>>
>>
>> Yes, you are a dinosaur :P
>
> /me waves a stack of punch cards at you and yells "Get off my lawn!".
>

LMAO !! I remember those ;)

>>> My LuaJIT experiments last year used Ubuntu 12.04, and I used
>>> LuaJIT git HEAD at the time.  This year I have tried the released
>>> 2.0.1 from that PPA I mentioned, and a couple of things broke.
>>> I've not actually tried Quakers commit yet.  LuaJIT is up to 2.0.2,
>>> released mid last year, but I didn't find a PPA for that version.
>>> Yes, sometimes I do use bleeding edge software, but I don't force
>>> it on anyone else.  B-)
>>>
>>>
>>
>> Personally, I don't see this as being "forced" on anyone.
>>
>> "edje: use luajit by default, if you want lua use --enable-lua-old"
>>
>> Thus, for those that do not have luajit (or do not want it), you can
>> --enable-lua-old.
>>
>> Not "forced" on anyone :) "Forced" (imo) would be if there was no
>> available option(s) to change it.
>
> I was speaking in general by that point.  In my opinion too often the
> bleeding edge is forced down peoples throats.
>

Ahhh ok :) I thought you were speaking in terms of this actual commit 
forcing things. No worries ;)

dh



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to