[Pkg-osg-devel] Project pkg-osg approved in Alioth

[Alberto Luaces]

"Manuel A. Fernandez Montecelo" writes:

> Copyint this to the list...
>

[...]

> About the synchronization with upstream, OSG is not the linux kernel or 
> glibc -- I don't think that we'll worry about porting patches back and forth 
> between releases, in general.  I think that we will simply use a given 
> upstream version, be it stable or development; and only a selected few 
> patches will be added on top.  That's why I think that tracking all upstream 
> changes is unnecessary, and we can do either copying the .zip or file-by-
> file, but not having to preserve upstream's history.
>
> If we need finer-grained control later, we can do it, but I don't think that 
> we need so much detail now.  But if you think otherwise, no problem for me.

No, it's fine for me. What are the specific actions to take? I'm going
to make a proposition, but it's up to you to correct it since you have
more experience with git than me.

Manuel, as you said, a very convenient way to take is to syncronize the
source with every new debian package release. I think the natural "git
way" would be to have versioning dependent on branches. That way, we can
have experimental packages as well as security releases and the current
release all in the same repository, only by switching branches. For
example:

| Branch         | Description                                                      |
|----------------+------------------------------------------------------------------|
| 2.4.0-1+lenny1 | Security release. Stems from the 2.4.0 tag in master branch.     |
|----------------+------------------------------------------------------------------|
| master         | 2.8.3 in sid/testing → 2.10 when released → ...                  |
|----------------+------------------------------------------------------------------|
| 2.9.9          | Experimental package that could be eventually merged in "master" |

On a side note, maybe we should remove the OpenSceneGraph-2.8.3.zip file
since the source will be already unpacked for every version. If we also
get rid of the *orig.tar.gz one, can dpkg-builder regenerate it from the
unpacked source as well without thinking it is not a third party
package? The point is to automate the generation of those files in the
less time consuming way, and avoiding possible errors.

That way, every changeset could be like

openscenegraph-x.y.z/
→debian/
→OpenSceneGraph

Regards,

Alberto