Le 25/04/2014 10:11, gfo...@free.fr a écrit :
+1 not to duplicate repositories about the reason I made this
packaging, the initial goal was to build both debian and spec reusing
the same description. As i never finished this, i don't mind if
someone refactor/remove this, but I would suggest as much as possible
to have a single description, included at least for plugins in some
kind of getdescription method, that could be used everywhere, not to
duplicate description, and possibly translations.
Agreed on that.
We need somebody to sync the translations in Debian/Fedora(?), too.
I'd recommend detecting features rather than OS (autoconf philosophy)
- e.g. assign $apache_user/$apache_group once rather than writing
multiple install2_files_$distro functions.
If the Makefiles support DESTDIR, they can be reused by packaging, so
let's do that too.
Post-install scripts can be installed in the system and run by the
packaging on install.
I fully agree, to reuse as much as possible common install code, in
install-ng, debian and spec
especially because à the end rules file could be really very very simple
do you suggect a Makefile / plugin ?
I think plugins need one (1) generic Makefile.
Otherwise there'll be lots of boilerplate, like in the current
plugin/*/packaging/
I started some work on tuleap debian packaging, Raphael Hertzog made some good
work there
and I'll probably try to share the same approach on both side.
Good to know.
--
Sylvain
_______________________________________________
Fusionforge-general mailing list
Fusionforge-general@lists.fusionforge.org
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
