As someone here has mentioned before. Don't bother with ifdefs all around and littering the code. It's git, not svn, branches actually work nicely. Just use branches.
-- Tom. On 18/06/13 00:56, [email protected] wrote: > On Mon, Jun 17, 2013 at 8:50 PM, Doug Newgard <[email protected]> wrote: > >> ---------------------------------------- >>> From: [email protected] >>> To: [email protected] >>> Date: Fri, 14 Jun 2013 11:22:45 -0500 >>> Subject: Re: [E-devel] E-MODULES-EXTRA migration to git >>> >>> ---------------------------------------- >>>> Date: Fri, 14 Jun 2013 08:07:19 +0900 >>>> From: [email protected] >>>> To: [email protected] >>>> Subject: Re: [E-devel] E-MODULES-EXTRA migration to git >>>> >>>> On Fri, Jun 14, 2013 at 6:01 AM, Simon <[email protected]> wrote: >>>> >>>>> On 06/14/2013 04:04 AM, Davide Andreoli wrote: >>>>>> 2013/6/13 Tom Hacohen <[email protected]> >>>>>> >>>>>>> Hey, >>>>>>> >>>>>>> So, following up on: https://phab.enlightenment.83648org/T159< >>>>> https://phab.enlightenment.org/T159> >>>>>>> I'm migrating E-MODULES-EXTRA to git. >>>>>>> I'm going to create a repo per module. I'm just interested to know, >>>>>>> which modules would you guys like to see migrated? >>>>>>> >>>>>> Cool !! >>>>>> Please move places and penguins for me, I maintain both (penguins >>>>>> is a little outdated but I have plans to update it soon) >>>>>> >>>>>> THANKS :) >>>>>> >>>>>> and I vote for moving flame, rain and snow too >>>>>> >>>>>> davemds >>>>>> >>>>>> >>>>> >>>>> I use forecasts and photo, both work reasonably well for me. On >> openSUSE >>>>> we package the following, i know at least 1 person has requested and >>>>> tested each of these with e17 comp-scale (I know its broken atm), >>>>> empris, engage, forecasts, mail, moon and mpdule. They all work for e17 >>>>> but i think some were planning on being re written for e18 with >>>>> composite so if people object i don't mind leaving them out. >>>>> >>>> >>>> I vote for comp-scale and engage. They are very good showcase. >>>> Sadly they're broken atm though. >>>> Maybe we should summon jeff. >>>> >>>> Daniel Juyung Seo (SeoZ) >>> >>> comp-scale isn't broken. It won't repeat, but it works fine with E18. >> >> OK, I was wrong, I was building off of an older checkout. Hannes >> Janetzek's commit that says "follow e17 comp api changes" breaks it with >> E18. Gustavo Lima Chaves updated it for E18 then Hannes Janetzek changed it >> back. :( >> > > Back then e17 and e18 comp api were the same iirc. I would suggest if > someone is going to work on engage or comp-scale to use separate branches, > #ifdef E18 or anything that is consistent with the other modules to handle > building for both e versions. Or better write something new :) > > > Regards, > Hannes > > >>> >>>> >>>> >>>>> >>>>> Cheers, >>>>> >>>>> Simon Lees >>>>> -- >>>>> openSUSE enlightenment maintainer. >>>>> >>>>>>> -- >>>>>>> Tom. >>>>>>> >>>>>>> >>>>>>> >>>>> >> ------------------------------------------------------------------------------ >>>>>>> This SF.net email is sponsored by Windows: >>>>>>> >>>>>>> Build for Windows Store. >>>>>>> >>>>>>> http://p.sf.net/sfu/windows-dev2dev >>>>>>> _______________________________________________ >>>>>>> enlightenment-devel mailing list >>>>>>> [email protected] >>>>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>>>>>> >>>>>> >>>>> >> ------------------------------------------------------------------------------ >>>>>> This SF.net email is sponsored by Windows: >>>>>> >>>>>> Build for Windows Store. >>>>>> >>>>>> http://p.sf.net/sfu/windows-dev2dev >>>>>> _______________________________________________ >>>>>> enlightenment-devel mailing list >>>>>> [email protected] >>>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>>>> >>>>> >>>>> >>>>> >> ------------------------------------------------------------------------------ >>>>> This SF.net email is sponsored by Windows: >>>>> >>>>> Build for Windows Store. >>>>> >>>>> http://p.sf.net/sfu/windows-dev2dev >>>>> _______________________________________________ >>>>> enlightenment-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>>>> >>>> >> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Windows: >>>> >>>> Build for Windows Store. >>>> >>>> http://p.sf.net/sfu/windows-dev2dev >>>> _______________________________________________ >>>> enlightenment-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>> >> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> enlightenment-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> enlightenment-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
