Thread: Re: [CEDET-devel] Fw: automake project !
Brought to you by:
zappo
From: Eric M. L. <er...@si...> - 2007-10-13 13:31:29
|
Hi, There are two automake project types. One reads a pre-existing automake file, so you would just type in the AC_INIT line you want. For the EDE project style automake, where the automake file is managed entirely by EDE, I think the item you found was an oversight where I forgot to finish the implementation. If I remember rightly, I think the AC_INIT I was using at the time wanted the name of a file, such that if the file change, automake would rebuild itself. I would be very happy if you took a shot at finishing that implementation to provide AC_INIT with the right arguments, and made any other logical updates for newer versions of automake. The version of automake I wrote that implementation against was back perhaps 10 years ago. Thanks Eric >>> Pierre Lorenzon <de...@po...> seems to think that: > >Hi, > >I am starting using automake project type. > >I wonder why the AC_INIT command in configure.in is set to : >AC_INIT(Project.ede) > >Indeed in the autoconf manual it is recommended to set : >AC_INIT (PACKAGE, VERSION, [BUG-REPORT], [TARNAME]) > >That's what I deed before when I wrote my configure.in by >hand. Indeed if these informations are set correctly they >appear more or less when running ./configure --help and I find >it convenient for the user. > >I mean that package name and version are available in >project.ede file and could be set by ede ; as well as the bug >report address that might be determined automatically by >collecting certain emacs user variables. > >Should I do these implementations ? > >Moreover it would be more uptodate to call the configure.in >configure.ac but it's a very small detail ! > >Regards > >Pierre > |
From: Pierre L. <de...@po...> - 2007-10-13 20:38:32
|
Hi Eric, From: "Eric M. Ludlam" <er...@si...> Subject: Re[1]: [CEDET-devel] Fw: automake project ! Date: Sat, 13 Oct 2007 09:31:21 -0400 > Hi, > > There are two automake project types. One reads a pre-existing > automake file, so you would just type in the AC_INIT line you > want. OK I understand ! It does not appear in the documentation but I know that documentations might always be improved and that developers don't have always time to do ti ! > > For the EDE project style automake, where the automake file is > managed entirely by EDE, I think the item you found was an oversight > where I forgot to finish the implementation. > > If I remember rightly, I think the AC_INIT I was using at the time > wanted the name of a file, such that if the file change, automake > would rebuild itself. > > I would be very happy if you took a shot at finishing that > implementation to provide AC_INIT with the right arguments, and made > any other logical updates for newer versions of automake. The version > of automake I wrote that implementation against was back perhaps 10 > years ago. OK that's only what I want to know ! When something does not function the way I expect it would have to function I always ask if either the developer does not complete the job or I don't understand the system philosophy ! I f ther are lines of code to write I think I know emacs enough to do it ! I don't remember if ten years ago all these variables that handle user name and email address were already present in emacs : anyway they are today and can be used ! So I''l complete the code and send you a patch a soon as possible. By the way thanks for having integrated the modifications I made to eieio.el ! I can now use the cvs version of eieio and not the custom version I had on my system ! Regards Pierre |
From: Pierre L. <de...@po...> - 2007-10-14 13:16:06
|
Hi Eric, I started to investigate ede code. I see some modifications that might be done. I can send you patches corresponding to these modifications but I wonder me if it would not be more efficient if I had a cvs access. What do you think of creating a new branch that I could maintain and that you could merge to the project if you think that my work is good enough ? For the moment I have cvs access problems to sourceforge.net but I suspect that it is a firewall reason on my system since there is no problem when trying from another system. I can solve this minor bug ! Regards Pierre |
From: Eric M. L. <er...@si...> - 2007-10-16 01:44:30
|
If you have signed papers for the FSF for contributions to Emacs, then your proposal sounds good. If not, then I need to accept patches instead. Here is a URL about it: http://www.gnu.org/prep/maintain/maintain.html#Legal-Matters If your patches are small (< 10 significant lines) then I usually just accept changes. If changes are large, then I have to figure out an alternative, such as dealing with the above legal issues, or re-writing the patch. Thanks for your help! Eric >>> Pierre Lorenzon <de...@po...> seems to think that: > >Hi Eric, > >I started to investigate ede code. I see some modifications >that might be done. I can send you patches corresponding to >these modifications but I wonder me if it would not be more >efficient if I had a cvs access. What do you think of creating >a new branch that I could maintain and that you could merge to >the project if you think that my work is good enough ? For the >moment I have cvs access problems to sourceforge.net but I >suspect that it is a firewall reason on my system since there >is no problem when trying from another system. I can solve this >minor bug ! > >Regards > >Pierre > -- Eric Ludlam: za...@gn..., er...@si... Home: http://www.ludlam.net Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net GNU: www.gnu.org |
From: Pierre L. <de...@po...> - 2007-10-16 19:47:38
|
Hi Eric, From: "Eric M. Ludlam" <er...@si...> Subject: Re[2]: [CEDET-devel] Fw: automake project ! Date: Mon, 15 Oct 2007 21:44:20 -0400 > If you have signed papers for the FSF for contributions to Emacs, then > your proposal sounds good. If not, then I need to accept > patches No I didn't but I can do it. Anyway I don't understand reading the document you mentioned what I exactly have to do step by step. Should I first create a gnu account for myself ? How ? Regards Pierre |
From: Eric M. L. <er...@si...> - 2007-10-20 14:26:28
|
Hi, I suspect that document is targeted more at me. The important bit is likely: > If you are not sure what to do, then please ask as...@gn... for > advice; If you write to GNU directly at the above address explaining you would like to assign copyright to the FSF for large changes to CEDET they will know what to do / send you. Many big contributions I put directly into cedet/contrib as that makes it clear (to me at least) what the current assignment state is, and easy to separate the two. If you change ends up being small (like some of your contributions to EIEIO) then this is not necessary, but based on your description, I expect your changes will be large. Thanks Eric >>> Pierre Lorenzon <de...@po...> seems to think that: > >Hi Eric, > >From: "Eric M. Ludlam" <er...@si...> >Subject: Re[2]: [CEDET-devel] Fw: automake project ! >Date: Mon, 15 Oct 2007 21:44:20 -0400 > >> If you have signed papers for the FSF for contributions to Emacs, then >> your proposal sounds good. If not, then I need to accept >> patches > > No I didn't but I can do it. Anyway I don't understand > reading the document you mentioned what I exactly have to do > step by step. Should I first create a gnu account for myself > ? How ? > > Regards > > Pierre > |
From: Pierre L. <de...@po...> - 2007-10-20 15:27:17
|
Hi Eric, From: "Eric M. Ludlam" <er...@si...> Subject: Re[2]: [CEDET-devel] Fw: automake project ! Date: Sat, 20 Oct 2007 10:26:20 -0400 > Hi, > > I suspect that document is targeted more at me. The I'd say that as weel ! > important bit > is likely: > > > If you are not sure what to do, then please ask as...@gn... for > > advice; > > If you write to GNU directly at the above address explaining you > would like to assign copyright to the FSF for large changes to CEDET > they will know what to do / send you. Then I'll try that ! > > Many big contributions I put directly into cedet/contrib as that > makes it clear (to me at least) what the current assignment state is, > and easy to separate the two. OK even if cvs could probably provide the functionality : anyway I started using cvs a few months ago and am not a cvs expert at the moment ! > > If you change ends up being small (like some of your contributions > to EIEIO) then this is not necessary, but based on your description, I > expect your changes will be large. Possibly indeed ! Anyway it might be a good thing for me to make this fsf subscription. > > Thanks > Eric > Bests Pierre |