Hello,
On 2014-08-18 09:56, Boudewijn Rempt wrote:
I know we sort of decided to only do this after 2.9, but I just picked
up Jonathan Riddell's discussion on irc on how our current repository
and release makes life harder for packagers -- basically a split up
repo would be easier, apparently.
Do they want separate repository or separate tarballs ? Because, I would
think that what they really want is the later, and separate repository
create some inconveniences for developers (and submodules have its own
set of caveats).
So an alternative would be to keep one repository, with "folders" that
are then packaged separately.
The way I see it:
* separate repositories
advantage: release manager friendly, since it has already a "tarball"
structure the build should be well tested
inconvenient: developer unfriendly, make it more difficult to move
code, have synchronizations issues (not sure if bisect will work
well)...
* single repository split in multiple tarballs
advantage: developer friendly
inconvenient: release manager unfriendly, since developers would still
be building as a single unit, there might be some rough edge after
splitting up
That said, I am not even sure that "single repository split in multiple
tarballs" is that release manager unfriendly, and we probably can make
it so that it is not.
--
Cyrille Berger Skott
_______________________________________________
calligra-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/calligra-devel
