On 04/05/16 08:27, Gordan Bobic wrote: > On 2016-04-05 06:09, Bjarne Saltbæk wrote: >> Depends on how you want to organize the code. Today i create a git >> repo per package ending up in appr. 5800 repos. It is ineffective to >> check out all packages each time you want to build just one package. >> With individual repos i assume using the issue/bug feature is good. If >> you using one repo with all rsel specs in it i fear it will end up in >> a big mess. > > Indeed, I figured it would be a case of having one repository per > src.rpm.
For RSEL7 I now have less than 40 patches. If we would only do the changed packages, I think it would be workable. > >> That said, i havent tried using it this way - but i remember that >> browsing RepoForge's github repo (with all specs in one repo) often >> crashed my browser :/ > > I cannot say that surprises me. > > Gordan > _______________________________________________ > users mailing list > [email protected] > https://lists.redsleeve.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://lists.redsleeve.org/mailman/listinfo/users
