On Wed, Feb 12, 2020 at 02:05:11PM -0500, Matthew Miller wrote: > On Wed, Feb 12, 2020 at 03:22:03PM +0100, Pierre-Yves Chibon wrote: > > > We've already migrated source RPM version control systems twice (from > > Just a small correction here, there was no migration when we put pagure on the > > top of dist-git. Repos didn't move nor the tooling that packagers are using. > > Okay, fair -- but if we lump that together with the pkgdb deprecation, > tooling _did_ change. Fair :) > > > > 12. > > > > As anyone, I want the URI to the archive (tar.xz, tar.bz2, etc) > > > > corresponding to various code states (commit/tag/release/fork…) to be > > > > regular and stable (ideally, identical to the Pagure URIs to avoid > > > > reimplementing existing automation) so that I can point to point-in-time > > > > snapshots of the repository. > > > > > > This feature seems key for possibly moving to or adding a "source git" > > > approach. > > > > The source git idea, as I understand it, is about using the exploded git repo > > and generate a tarball locally, so not relying on the forge hosting the repo. > > We need to have some way to guarantee that a given reference to source > control in which the "exploded" repo lives is always the same thing and > can't be changed underneath us. My understanding was that we could simply store these exploded repo in dist-git where history cannot be changed, thus guaranteeing this consistency. Pierre _______________________________________________ council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
