[Pkg-gridengine-devel] SGE on Debian Unstable

[Laszlo Kajan]

Hello Dave!

>>>>> I was assuming only the packaging would be maintained there, producing a
>>>>> debian.tar.gz which would just work with the sge distribution tarball.
>>>>> Why does it need the whole tree there?
>>>>
>>>> This is the standard work-flow when using git for packaging (as opposed
>>>> to when using subversion).  
>>>
>>> Is this stuff documented somewhere?
>>
>> So, yes, I wanted to prepare a wiki page we all can contribute to, on git usage, and package building: [1].
>>
>> [1] http://wiki.debian.org/GridenginePackaging/GitGuide
> 
> I still don't understand why the whole source needs to be in the repo,
> but never mind.  I added a watch file already.  I won't have a chance to
> try to understand the git stuff immediately.

The way I understand it now: in order to build, you always need the upstream. With git, it is kept in the git repository, not in a tarball. With
SVN (with mergeWithUpstream) it would be kept in a tar.gz. New versions of upstream tarballs are imported into the git repo cleverly, with
pristine-tar, which records only changes, and keeps the repository small.

> Why do built files (template, at least) need to go in the repo?

Oh, sorry, I did not realize these were generated from debian/gridengine.templates! Then of course there is no need to include them!

Best regards,
Laszlo