Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

svn complete replacement for externals #243

Open
andry81 opened this issue Jul 4, 2022 · 1 comment
Open

svn complete replacement for externals #243

andry81 opened this issue Jul 4, 2022 · 1 comment

Comments

@andry81
Copy link

andry81 commented Jul 4, 2022

I am looking for git/svn complete replacement.

Is not clear how the tool would checkout a repo for SVN with following parameters.

To replace svn-external by a record in the vcstool repo configuration file, I have to somehow translate 2 revisions into vcstool format. The PEG revision AND the OPERATIVE revision, which can be used, for example, to fixate an external to a particular revision in a tag (on a date of the commit the tag is created from/for).

Documentation: https://svnbook.red-bean.com/en/1.6/svn.advanced.pegrevs.html

The SVN revisions format for an external:

-r "OPERATIVE_REV" "URL@PEG_REV" "PATH"

I can convert 2 revisions into 1 manually, using the documented algorithm in the SVN book. But nevertheless the SVN can use a date as a revision:

-r "{2021-03-01 05:37:58 +0300}" "...@{2021-03-01 05:37:58 +0300}" ...

Why this has a sense? Because in SVN you can fixate an external repository revision as a date of a parent repository revision. How that translate into the vcstool?

@andry81
Copy link
Author

andry81 commented Mar 17, 2023

Seems this PR has a change with sparse checkout implementation which is a most closest to svn:externals replacement:

#218
https://github.com/dirk-thomas/vcstool/pull/219/files

Everything else after translation into the git can be just dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant