On 13/11/16 16:55, Bjarne Saltbæk wrote:
Hi Jacco.
What is your ideas about Github?
As you can see I tried putting my RSEL spec files into Github, but I
think it is going to be a big mess. You will need to download all spec
files + all patches + all changes each time you want to build/work on
just one package.
This is a fair point, but there is a practical issue, specifical that of
creating 2000 or so repositories.
In reality, even back in the day of RSEL 6.0 only about 120 or so spec
file changes were needed, and only a fraction of those needed additional
patches. This is a reasonably practical amount to keep in a single
repository, or at least more practical than having a separate repository
for every package that needs changes. Additionally, it makes it not
obvious how to deal with cases where a package used to need a patch but
no longer does. With a single repository we simply remove the spec file
and the patch. In the case of one repository per package, do we delete
the whole repository?
As you can see on my git server (at https://gitserver.dev.saltbaek.dk) i
prefer 1 repo per package. Gitbit has that feature that it can do
projects so it can group repositories in bigger repositories - just
saying ;)
I can understand the appeal of grouping repositories, but I'm not sure
it outweighs the benefits of using a widely used hosted solution like
github. It makes it so much easier to engage with the project.
Having said that, there does seem to be a way to do a sparse checkout
using git:
https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository
I haven't tried to do that with a github backed repository yet.
Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
