Extend github sourcing to any git repo

[jonathanmorley]

There should be support for any git repository to be sourced as a package.

This could be done with a similar syntax to npm:

git://github.com/user/project.git#commit-ish
git+ssh://user@hostname:project.git#commit-ish
git+ssh://user@hostname/project.git#commit-ish
git+http://user@hostname/project/blah.git#commit-ish
git+https://user@hostname/project/blah.git#commit-ish

[forki]

how does npm handle the download? does it assume git is in path?

[dnauck]

@forki don't forget that Paket is used mostly on Windows. So users don't have git installed but some GUI clients with internal git, etc. You should not compare it with tools for unix platforms where everything is in path.

[khellang]

So users don't have git installed but some GUI clients with internal git, etc.

LOL. That's not true at all. Even if you use GitHub for Windows, you still have git in your PATH.

[forki]

I don't think paket is mostly used on Windows, but yes git is not
everywhere yet.
We support the github repo because it's easy to download. Https get +
unzip. Done
On Oct 22, 2014 9:42 AM, "Daniel Nauck" [email protected] wrote:

@forki https://github.com/forki don't forget that Paket is used mostly
on Windows. So users don't have git installed but some GUI clients with
internal git, etc. You should not compare it with tools for unix platforms
where everything is in path.

—
Reply to this email directly or view it on GitHub
#284 (comment).

[dnauck]

@khellang I don't know why you get personal, but the default for msysgit on Windows it to be not on PATH:

@forki If you target .NET developers with Paket than it is mostly used on Windows. So just check if git is in PATH, if not fallback to NGit or whatever

[jonathanmorley]

https://www.npmjs.org/doc/misc/npm-config.html#git

git
Default: "git"
Type: String
The command to use for git commands. If git is installed on the computer, but is not in the PATH, then set this to the full path to the git binary.

npm has a config option where you can give it a path to git if its not in your path

[forki]

That's exactly how we do it in FAKE. Seems the way to go.
On Oct 22, 2014 8:32 PM, "Jonathan Morley" [email protected] wrote:

https://www.npmjs.org/doc/misc/npm-config.html#git

git
Default: "git"
Type: String
The command to use for git commands. If git is installed on the computer,
but is not in the PATH, then set this to the full path to the git binary.

npm has a config option where you can give it a path to git if its not in
your path

—
Reply to this email directly or view it on GitHub
#284 (comment).

[yannisgu]

Maybe using libgit2sharp would be better than using git command?

• No assumpotion about git installation
• Cleaner API probably (.NET vs exec)
• Better error handling with exceptions

• Yet another library
• No SSH auth support yet: Repository.Clone doesn't support SSH libgit2/libgit2sharp#255
• Not all features of git are supported

Not sure what's better..

But 👍 for the idea!

[AlexZeitler]

👍

[caindy]

Is this the right place to (suggest / ask for) support for private github repos?

[isaacabraham]

@caindy Probably a new issue I would've thought? @forki

[ilkerde]

I strongly support this feature to be implemented with "git in path". If git is not available, paket can politely tell the user to require it.

Thanks for your work!

[forki]

There is a first alpha version available. This feature will come with Paket v3.

[CumpsD]

Are you using LibGitSharp now? If so, I thought it didn't support SSH repositories, or has that changed?

[caindy]

@CumpsD according to the documentation

This feature assumes that you have git installed. If you don't have git installed then Paket still allows you to reference files from github.

[CumpsD]

@caindy yes I know, I was referring to the comment of @yannisgu higher in this thread who proposed libgit2sharp, upon which my mind sprung to the fact it apparently doesn't wrap ssh yet.

[forki]

We use the installed git.exe
On Jan 8, 2016 20:37, "David Cumps" [email protected] wrote:

@caindy https://github.com/caindy yes I know, I was referring to the
comment of @yannisgu https://github.com/yannisgu higher in this thread
who proposed libgit2sharp, upon which my mind sprung to the fact it
apparently doesn't wrap ssh yet.

—
Reply to this email directly or view it on GitHub
#284 (comment).

[jschiefer]

I have been playing with this and have a little trouble understanding the use model. I want to pull down a whole git repository, so I put a "git" line into the paket.depedencies and install, and it does that just fine. But where do I go from here?

I expected I would run a build using the build:"build.cmd" syntax, and then somehow be able to refer to the build artifacts in the appropriate paket.references files. From looking at the code, it appears that the file: syntax in paket.references would be one way this might work. Or is building a Nuget file as described at the bottom of http://fsprojects.github.io/Paket/git-dependencies.html the correct way to do this?

Background: I was hoping to use Paket as an easy way to switch between binary (NuGet) and source (git repo) references for individual packages, for cases where you occasionally need to debug into a library..

[forki]

At the moment the only supported way is building nuget packages. But we
also want to allow more use cases. What do you want to achieve? Referencing
dlls
?
On Jan 12, 2016 07:19, "Jan Schiefer" [email protected] wrote:

I have been playing with this and have a little trouble understanding the
use model. I want to pull down a whole git repository, so I put a "git"
line into the paket.depedencies and install, and it does that just fine.
But where do I go from here?

I expected I would run a build using the build:"build.cmd" syntax, and
then somehow be able to refer to the build artifacts in the appropriate
paket.references files. From looking at the code, it appears that the file:
syntax in paket.references would be one way this might work. Or is building
a Nuget file as described at the bottom of
http://fsprojects.github.io/Paket/git-dependencies.html the correct way
to do this?

Background: I was hoping to use Paket as an easy way to switch between
binary (NuGet) and source (git repo) references for individual packages,
for cases where you occasionally need to debug into a library..

—
Reply to this email directly or view it on GitHub
#284 (comment).

[jschiefer]

Yes, referencing assemblies. Let's say in my fsproj I have a reference to a dependent assembly that I satisfied via Paket/NuGet. I would be able right-click on the reference in the solution explorer and select a "get source" menu entry, which would, via Paket, retrieve the source repository for the dependent assembly, load its corresponding csproj file and replace any reference to the binary with a project reference throughout the solution. Bascially a low-friction way to go from binary/Nuget to source/git and back as needed.

[forki]

how about this (potential feature):

in paket.references:

// project: paket-files/.../MyNuGet.csproj
// MyNuGet

By uncommenting one of the two lines and running "paket install" you could enable the corresponding setting.

[forki]

maybe we can do it in the same line!?

[jschiefer]

Initially this sounded like a good proposal, but let's think about the implications:

I assume there would need to be two entries for MyNuGet in the paket.dependencies: one for the Nuget, and one for the source, and they would need to be tied together somehow. The "obvious" assumption that the NuGet package name corresponds to the git repository name is probably invalid.

Which git commit would Paket select on install or update? Initially, you would want whatever is specified in paket.dependencies. But if you switch to source, you would eventually make changes, so now your local repository under paket-files is in a different state. Then what should Paket do on install or update? Should an update change the version specification in paket.lock to be different from paket.dependencies?That doesn't sound right...

Also, what if you had two references to MyNuGet in different projects, where one used the NuGet binary and the other used the source version from git, you'd end up with two different versions of MyNuGet in the end, which is not what you want. So maybe the switching needs to happen in paket.dependencies, not paket.references, for that reason?

Should we discuss this in #334?

[forki]

yes #334 is better place

[forki]

Implemented in v3

[Thorium]

How do I reference a private git (e.g. Bitbucket) repo? Will it ask password on every build or can it be set as env variable? https://fsprojects.github.io/Paket/git-dependencies.html didn't have any info of private repositories...

[forki]

It uses your local git installation and will use password from it's password store / ssh key Tuomas Hietanen <[email protected]> schrieb am Do., 30. Aug. 2018, 21:20:

…

How do I reference a private git (e.g. Bitbucket) repo? Will it ask password on every build or can it be set as env variable? https://fsprojects.github.io/Paket/git-dependencies.html didn't have any info of private repositories... — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#284 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNA3yGZ0SONL1z3CTyQAOd0rO9h6Aks5uWDr2gaJpZM4CxeS4> .