On Fri, 25 Feb 2005 16:34:54 +0100 Richard Torkar <[EMAIL PROTECTED]>
(Bbabbled:
(B
(B> 
(B> Hi all,
(B> 
(B> I've been looking at improving the build system that the different E
(B> modules have. At the moment there is no automatic creation of *.spec
(B> files when running autofoo.
(B> 
(B> My proposal is to (foreach module) add the functionality so that the
(B> spec file is automagically created and populated with the correct info
(B> thus making it much easier to create rpms directly from CVS. 
(B> 
(B> I.e. making this in the future would be possible:
(B> cvs co e17/libs/ecore
(B> [...]
(B> cd ecore && ./autogen.sh --prefix=/usr --sysconfdir=/etc
(B> Now the *.spec.in file is transformed into a *.spec file which can be
(B> used to easily create rpms. Version number et al. are automagically
(B> fixed by autofoo et al.
(B> 
(B> As an example I have attached a diff for ecore which solves this
(B> problem. Attached is also the ecore.spec.in file that is needed for this
(B> (cvs add). The old ecore.spec file should thus be removed (cvs rm)...
(B> 
(B> Is this something that will be accepted by the developers? If so, I'll
(B> continue preparing the rest of the modules. At the moment I'll use plain
(B> diff, but removing and adding files is not possible for me since it
(B> requires write access to CVS.
(B
(Bthere is one problem - we also have debian packaging files, not just .spec. we
(Balso have .bb and .oe packaging files... there's mroe than just .spec to fix. :)
(B
(B
(B-- 
(B------------- Codito, ergo sum - "I code, therefore I am" --------------
(BThe Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
$BMg9%B?(B                              [EMAIL PROTECTED]
(BTokyo, Japan ($BEl5~(B $BF|K\(B)
(B
(B
(B-------------------------------------------------------
(BSF email is sponsored by - The IT Product Guide
(BRead honest & candid reviews on hundreds of IT Products from real users.
(BDiscover which products truly live up to the hype. Start reading now.
(Bhttp://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
(B_______________________________________________
(Benlightenment-devel mailing list
([email protected]
(Bhttps://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to