Hi,
Le 2014-08-05 09:22, Roland Mas a écrit :
Sylvain Beucler - Inria, 2014-08-04 17:34:20 +0200 :
Hi,
One question is where to make the changes: 5.3 or master?
So far the only changes that have been committed are those "under the
hood". Paths have not changed, only the way to get them. This has been
committed both to 5.3 and master.
OK.
I'd recommend not committing anything on the stable branch but bugfixes
and additions that we direly need.
Otherwise we just risk introducing bugs with no benefit.
(that's basically why I didn't work on the installation system until
now, heh)
- As I mentioned before my vacation I plan to start work on the Grand
Unified Makefile this week, and that will impact the Debian and RPM
packaging.
Will it be autotools-based? AKA, "./configure && make && make install"?
Last time we discussed it with Christian, no.
Autotools is well-suited for C/C++ projects but adds a layer of
complexity and caching (and we don't need to C/C++ niceties).
We can do that work either on master or on a "GUM" branch - thoughts?.
How about making the gforge->fusionforge transition at the same place
to avoid conflicts?
Good idea. I suggest starting on a branch, but with an eye on merging
into master as soon as possible. I can help setting up CI jobs if
needed :-)
I'll start the branch then, hopefully this will be usable within next week.
- I'm not sure why we pushed changes on the 5.3 stable branch already,
do we need the renaming right now, or can this wait 5.4?
(aka I'm now afraid to upgrade my prod ;))
The actual change of the paths (and package names…) should not go into
5.3, I think.
I think the same :)
--
Sylvain
_______________________________________________
Fusionforge-general mailing list
Fusionforge-general@lists.fusionforge.org
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
