[Caml-list] Creating fresh OPAM repository

[Caml-list] Creating fresh OPAM repository

[Dario Teixeira]

Hi,


How does one create a fresh repository with OPAM?  The documentation has plenty
of examples of cloning existing repos, but what I want is to start an empty one on the
local filesystem.  Does the OPAM tool have some option for this, or is one supposed
to do it "by hand", ie, create a filesystem structure that mimics existing repos?

Best regards,
Dario Teixeira

Re: [Caml-list] Creating fresh OPAM repository

[Thomas Gazagnaire]

Hi Dario,

> How does one create a fresh repository with OPAM?  The documentation has plenty
> of examples of cloning existing repos, but what I want is to start an empty one on the
> local filesystem.  Does the OPAM tool have some option for this, or is one supposed
> to do it "by hand", ie, create a filesystem structure that mimics existing repos?

If you want to start an empty local repository in /foo/bar, just run:

$ opam remote local /foo/bar

(you can replace 'local' by any other name in the previous commands, it's just a way to identify the repository)

After that, you can:
* either populate it incrementally by adding the usual '/foo/bar/packages/NAME.VERSION/{opam,url,descr}' for package descriptions and '/foo/bar/compilers/VERSION+NAME.comp' for  compiler description. Don't forget to update your repository by doing 'opam update local' to take these changes into account; or
* use 'opam upload'. This is however not yet tested as well as the first solution. If you use it and found some issues, please do not hesitate to fill a bug.

--
Thomas

Re: [Caml-list] Creating fresh OPAM repository

[Dario Teixeira]

Hi,

> If you want to start an empty local repository in /foo/bar, just run:

> 
> $ opam remote local /foo/bar
> 
> (you can replace 'local' by any other name in the previous commands, 
> it's just a way to identify the repository)

Thanks for the prompt reply, Thomas.  The command you suggested
does not seem to work, at least with OPAM version 0.8.1.

The error message suggests that one of -add, -rm, or -list must be given.
However, all the following fail:

  opam remote -add local /foo/bar
  opam remote -add local file:///foo/bar
  opam remote -add -kind local local /foo/bar
  opam remote -add -kind local local file:///foo/bar

The 'remote' subcommand seems to expect an already formed repository
at the given address.

Any ideas?

Thanks in advance!
Dario Teixeira

Re: [Caml-list] Creating fresh OPAM repository

[Anil Madhavapeddy]

On 11 Dec 2012, at 16:31, Dario Teixeira <darioteixeira@yahoo.com> wrote:

> Hi,
> 
>> If you want to start an empty local repository in /foo/bar, just run:
> 
>> 
>> $ opam remote local /foo/bar
>> 
>> (you can replace 'local' by any other name in the previous commands, 
>> it's just a way to identify the repository)
> 
> Thanks for the prompt reply, Thomas.  The command you suggested
> does not seem to work, at least with OPAM version 0.8.1.
> 
> The error message suggests that one of -add, -rm, or -list must be given.
> However, all the following fail:
> 
>   opam remote -add local /foo/bar
>   opam remote -add local file:///foo/bar
>   opam remote -add -kind local local /foo/bar
>   opam remote -add -kind local local file:///foo/bar
> 
> The 'remote' subcommand seems to expect an already formed repository
> at the given address.

Just mkdir the directory first.  There's nothing special about a local remote
except that a "packages" directory is expected.

$ mkdir -p /foo/bar/packages
$ opam remote -add local /foo/bar

should (hopefully) do the trick.

-anil

Re: [Caml-list] Creating fresh OPAM repository

[Thomas Gazagnaire]

> Just mkdir the directory first.  There's nothing special about a local remote
> except that a "packages" directory is expected.
> 
> $ mkdir -p /foo/bar/packages
> $ opam remote -add local /foo/bar
> 
> should (hopefully) do the trick.

Indeed, sorry for the confusion, you need to add '-add' and /foo/bar must already exists (and can be empty -- the package subdir is not mandatory).

Thomas

Re: [Caml-list] Creating fresh OPAM repository

[Dario Teixeira]

Hi,

> Just mkdir the directory first.  There's nothing special about a local 

> remote
> except that a "packages" directory is expected.
> 
> $ mkdir -p /foo/bar/packages
> $ opam remote -add local /foo/bar
> 
> should (hopefully) do the trick.

Yes, that did the trick -- thank you!  The only other "tricky" thing
I came across is that the individual package directories under
'packages' should be named using a dot to separate the package
name from the package version (probably because the customary
dash would be ambiguous, since it also appears frequently in
package names)...

Best regards,
Dario Teixeira