On 8 Jun 2014, at 10:04 pm, Hin-Tak Leung <[email protected]> wrote:
> Hmm, maybe my message wasn't clear enough. (1) An empty > file called "git-daemon-export-ok" needs to be created if you want a directory > to be exported by the git daemon, (2) anything downloadable > (http/ftp/rsyc/scp) > is usually git clone'able. git clone even operates over local directories; > there > are no additional configuration for these. > > I think there were some confusion about what 'go get' does. it probably > does not involve git. “go get path.git” tries to clone a repository located at the given path (without the “.git” ending) by doing the following, I think in this order: - git clone git://path - git clone http://path - git clone https://path The problem I brought up is caused by the removal of the “.git” suffix from the argument of “go get”. It can be solved by either: 1. Make the repository available at http://git.spdx.org/spdx-tools-go (without the .git ending) 2. Use another feature of go get and add a <meta> tag to spdx.org (and /spdx, /tag, /rdf) which directs the go get command to the correct repository. >From my command line: $ git clone http://git.spdx.org/spdx-tools-go Cloning into 'spdx-tools-go'... fatal: repository 'http://git.spdx.org/spdx-tools-go/' not found $ git clone http://git.spdx.org/spdx-tools-go.git Cloning into 'spdx-tools-go'... remote: Counting objects: 140, done. remote: Compressing objects: 100% (136/136), done. remote: Total 140 (delta 71), reused 0 (delta 0) Receiving objects: 100% (140/140), 33.68 KiB | 0 bytes/s, done. Resolving deltas: 100% (71/71), done. Checking connectivity... done. > > -------------------------------------------- > On Sun, 8/6/14, Gary O'Neall <[email protected]> wrote: > > Subject: RE: [GSOC] Make the Go library "go get"-able > To: [email protected], "'Vlad Velici'" <[email protected]>, > [email protected], "'Jack''Manbeck'" <[email protected]> > Date: Sunday, 8 June, 2014, 20:57 > > Just to clarify - I only > have access to the gitolite config file to > configure git access. I do not have access to > the server itself. > > I do > admit I am not a git expert, so any advice or pointers is > appreciated. > > If there is a > configuration option to solve Vlad's problem, please > be > specific on the configuration changes. > If there is something that Vlad can > do in > accessing the repository differently, please be specific on > what steps > can be taken. > > Thanks, > Gary > >> -----Original > Message----- >> From: Hin-Tak Leung > [mailto:[email protected]] >> Sent: Sunday, June 8, 2014 12:49 PM >> To: 'Vlad Velici'; [email protected]; > Jack''Manbeck; Gary >> > O'Neall >> Subject: RE: [GSOC] Make > the Go library "go get"-able >> > >> > -------------------------------------------- >> On Sun, 8/6/14, Gary O'Neall <[email protected]> > wrote: >> >>> I > was >> not able to find an easy way to > make the git repo cloneable without >> > the ".git". We are using gitolite to configure > the repositories, so >> if there are any > git experts on the mailing list with a solution, >> pls. let me know. >> > >> That sounds rubbish. Although git has > its own protocol (git://, over >> port > 9418), it can operate over ftp, http, rsync, etc and a dozen > of >> other network protocols also > also. >> A non-exhaustive list is at the > bottom of "man git-clone". >> > >> Though, it is not often documented > that a directory needs to have an >> empty > file "git-daemon-export-ok" to be acted on by the > git server >> daemon. Please just read up > on that. > _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
