elementary-dev-community team mailing list archive

[Lucas Baudin <xapantu@xxxxxxxxx>]

Hi,

Just to clarify my opinion, I also think that the fork is a good idea
here (we already discussed about that several times on IRC), I was only
speaking about the CMake thing :)

Lucas

Le jeudi 05 janvier 2012 à 14:14 -0800, Daniel Foré a écrit :
> Well, I don't think it's unrealistic to expect that we can have our
> own desktop. We're attracting more and more developers as time goes
> on. And I think the example of Ne kind of backfires because we now
> have Marlin instead. So, if Mario wants to just fork and thinks he can
> maintain the app himself, I don't see anything wrong with that.
> 
> 
> However, I do have to agree with Lucas that if the current build
> system works just fine I don't see a real reason to change it. 
> 
> Best Regards,
> Daniel Foré
> 
> 
> www.elementaryos.org
> 
> On Jan 5, 2012, at 1:54 PM, xapantu <xapantu@xxxxxxxxx> wrote:
> 
> 
> 
> > Just, before you read this mail, this is your project, so, of
> > course, you can do what you want ;) Here are only some advice.
> > 
> > 
> > No, sorry, it is a bad idea. We don't have the man power to maintain
> > a full desktop (sorry, back to reality for most of the elementary
> > team, but we won't be able to maintain all the pantheon desktop if
> > we don't reuse most of the code). You can't really imagine merging
> > upstream changes if you don't keep the build system. Maybe, right
> > now, you think you will never merge again, but, we saw this in the
> > past, with nautilus elementary, you'll have to (what about gtk4?
> > what about new features you don't expect? etc...).
> > 
> > The other point is that the autotools are not evil. They work really
> > nice when they are well used. Here, the build system perfectly
> > works, it is stupid to maintain two build system. And, it is even
> > useless to spend time on a CMake conversion, you will have to
> > re-write the HOW-TO-BUILD docs, etc...
> > 
> > 
> > Lucas
> > 
> > 2012/1/5 Mario Guerriero <mefrio.g@xxxxxxxxx>
> >         Hi,
> >         
> >         As you probably know I am working on a Vala version of
> >         Dexter using gnome-contacts codebase. It is something
> >         similar a fork and I want to move its build system to CMake
> >         as the others elementary apps but for this I need a very
> >         CMake expert because I don't know how to make it!
> >         https://blueprints.launchpad.net/dexter-contacts/+spec/cmake-build-system
> >         I know that this will broke the upstream compatibility but I
> >         don't want to follow the gnome-contacts developers anymore
> >         for a few reasons. The contacts store system is stable and
> >         it will automatically be improved at every release of folks
> >         with feature as the Windows Live support. Also the upstream
> >         dev started to follow an UI design way that I don't like,
> >         and probably the designers too. For example they created a
> >         dialog to add contacts but I (and lallenlowe) want it
> >         in-window as it is now. So Dexter will be more a fork, and
> >         not just a code modification.
> >         
> >         I also want to release an initial version of the project
> >         after the porting to CMake
> >         
> >         Best regards, 
> >         Mario
> >         
> >         
> >         --
> >         Mailing list:
> >         https://launchpad.net/~elementary-dev-community
> >         Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> >         Unsubscribe :
> >         https://launchpad.net/~elementary-dev-community
> >         More help   : https://help.launchpad.net/ListHelp
> >         
> > 
> > 
> > -- 
> > Mailing list: https://launchpad.net/~elementary-dev-community
> > Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~elementary-dev-community
> > More help   : https://help.launchpad.net/ListHelp
> >