|
Hi Olek and others,
the only reason against merging versions pre 1.9 is that it will
cost some time and most likely nobody is ever going to look at it?
Maybe it would be sufficient to have a new "ogre" repo and start
1.12 as a branch of this? (ogre-1.9 has no common history with
attic/ogre)
I commited my changes to a fork of the "ogre-1.9" repo in my
namespace and would suggest to move/copy this to debian-games/ogre
if approved
https://salsa.debian.org/simonschmeisser-guest/ogre-1.9
https://mentors.debian.net/package/ogre-1.12
Thanks
Simon
On 23.11.19 18:17, Olek Wojnar wrote:
Hi Simon,
I'm not sure why the ogre package was ever split across
three different repositories. I suspect that it was done by
someone who was not very familiar with git and didn't
understand branches and tags. I think that the best way
forward would be to merge both the 1.8 and 1.9 repositories
into the attic/ogre repository and make that the main
repository that we use for all OGRE packages in Debian. Are
you comfortable enough with git, and how history works in git,
to do that? Do you see any reason to NOT merge into a single
repository?
Take a look at CEGUI [1] (one of the packages I help
maintain) to see how the entire history of a library project
is in a single repository with tags designating each release.
-Olek
Hi Olek,
Just to clarify: You would like me to continue with the
ogre-1.9 repository, with the attic/ogre (which contains
ogre-1.7) or copy the existing ogre-1.9 to a new "ogre"?
Thanks
Simon
On 23.11.19 15:48, Olek Wojnar wrote:
<snip>
> There is
one git repository called "ogre" in attic which
contains
> ogre-1.7, do you mean this? I assumed I
should create a new repo called
> debian-games/ogre-1.12 and just copy the
debian files from 1.9 and add
> changes towards supporting 1.12 as commits on
top of that?
I'm not sure if we want to continue using
different ogre repositories.
In my opinion using one repository, maybe with
different branches, would
preserve the history. We can also create an
ogre-1.12 one if that helps.
As a downstream user of OGRE, I much
prefer using the existing repository. Tagging an
upstream release and putting updated sources in the
same repository is the best way of keeping everything
together. That also makes it easier when packages that
depend on OGRE have issues and their maintainers need
to dig into OGRE code to try to find regressions and
such.
Simon, please feel free to send me a
direct email (no need to copy the list) if you have
any questions or need any help merging into that
repository. I'll be happy to help!
-Olek
|