new salsa team: nvidia-team

Andreas Beckmann anbe at
Sat Jan 20 18:01:07 UTC 2018

On 2018-01-20 18:43, Luca Boccassi wrote:
>> Right, forgot that the original plan was to keep the tarballs in SVN
>> -
>> I'll go and look if git LFS is enabled on Salsa - I'm pretty sure
>> GitLab supports it.
> Did a quick test and it looks like LFS is enabled - committed a binary
> file in a non-default branch, pushed - then cloned a different branch
> elsewhere and it didn't download the binary until the branch was
> checked out.

we should probably have one ${REPO}-tarballs repository for each ${REPO}
with blobs, I don't think I want to mix them into ${REPO}
IIRC there are nvidia-cg-tookit, nvidia-cuda-toolkit and
nvidia-graphics-drivers. We should be OK losing all the nvidia-settings
etc. tarballs.

I still don't see how a workflow could look like ... we need some kind
of shallow clone by default with the option to retrieve older tarballs
easily ... (and without losing the current bits)
Having a subdirectory for each version may (or may not) be a good idea.

snapshot.d.o has only most of the tarballs, and it requires an accepted
upload before it can be used.


More information about the pkg-nvidia-devel mailing list