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

The SVN commands #54

Open
shmuelie opened this issue Apr 5, 2017 · 8 comments
Open

The SVN commands #54

shmuelie opened this issue Apr 5, 2017 · 8 comments

Comments

@shmuelie
Copy link

shmuelie commented Apr 5, 2017

I (sadly) have to work with SVN repositories at work and having the svn command work would be awesome. Has any though been put into them? Would there be any objection to me looking into getting them started?

@Jaykul
Copy link
Member

Jaykul commented Apr 6, 2017

I wouldn't object on principle, but I would be mildly surprised if they were accessible through libgit the way the rest of this is done...

@shmuelie
Copy link
Author

shmuelie commented Apr 6, 2017

Sadly, though I'm not shocked either, libgit doesn't expose the svn commands. Would you be apposed to my text parsing methods? I do admit this would mean a dependency on having git installed for using the SVN commands but that would only be to use them.

@Jaykul
Copy link
Member

Jaykul commented Apr 6, 2017

I think that once you have that completely different external dependencies, at that point I would suggest it's a separate module. I think @SamuelEnglard is working a similar module based on parsing git.exe (see #53), it might be a better fit? 😉

Sorry, I couldn't resist.

Honestly though -- I'm fine with the idea of putting SVN commands in this repo, just for the sake of collaborating on what things mean. I'm permanently disappointed that neither Posh-Hg nor Posh-Git was interested in my PRs to unify and make their configurations generic so I could share the prompt settings across them.

We should do it as a separate PSGit.SVN.psm1 or something though, which would take a RequiredModules = PSGit to connect them if there's

@shmuelie
Copy link
Author

shmuelie commented Apr 6, 2017

I deserved that 😛 lol

Sure. In my own work I found myself creating helper cmdlets that combined git and svn so not having to text parse the git side will be nice!

@shmuelie
Copy link
Author

In looking into git svn it's actually a perl script that calls SVN native or GIT native methods. Wondering if replacing that perl with PowerShell directly may be the solution.

@dahlbyk
Copy link

dahlbyk commented Apr 13, 2017

I'm permanently disappointed that neither Posh-Hg nor Posh-Git was interested in my PRs to unify and make their configurations generic so I could share the prompt settings across them.

Still sorry about that... I aspire to be a better maintainer than Keith of 2013. 😬 Fortunately, Git won so nobody cares about Hg anymore. 😀

@Jaykul
Copy link
Member

Jaykul commented Apr 15, 2017

Sad but true(ish). Github won the game for git.

@SamuelEnglard possibly. I don't know what the feature-set of git svn is, but I'm sure that if you were going to adopt a PowerShell wrapper for libgit as your source control interface, but needed to work against svn ... integrating migration/bridge stuff for SVN would be worth considering -- if you were going to do that, you could look for a .net assembly that would let you work directly on objects 😉

@shmuelie
Copy link
Author

@Jaykul you read my mind 😉

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

3 participants