Hi, 14.09.14 14:03, Michał Górny написав(ла): > Hi, > > I'm quite tired of promises and all that perfectionist non-sense which > locks us up with CVS for next 10 years of bikeshed. Therefore, I have > prepared a plan how to do git migration, and I believe it's doable in > less than 2 weeks (plus the testing). Of course, that assumes infra is > going to cooperate quickly or someone else is willing to provide the > infra for it. >
as always, nice effort, but I foresee lots of bikeshedding in this thread. ) > This means we don't have to wait till someone figures out the perfect > way of converting the old CVS repository. You don't need that history > most of the time, and you can play with CVS to get it if you really do. > In any case, we would likely strip the history anyway to get a small > repo to work with. > Is it so difficult to convert CVS history? > > The rsync tree > -------------- > > We'd also propagate things to rsync. We'd have to populate it with old > ChangeLogs, new ChangeLog entries (autogenerated from git) and thick > Manifests. So users won't notice much of a change. > How will user check the ebuild integrity with thick manifests using rsync? > The remaining issue is signing of stuff. We could supposedly sign > Manifests but IMO it's a waste of resources considered how poor > the signing system is for non-git repos. > Again, how will user check the integrity and authenticity if Manifests are unsigned? Also, it would be a good idea to add automatic signature checking to portage for overlays that use signing (or is it already done?). -- Jauhien
signature.asc
Description: OpenPGP digital signature
