Packaging of libraries

Dominique Dumont dod at
Tue May 23 19:01:47 UTC 2017

On Tuesday, 23 May 2017 18:30:20 CEST Daniel Dehennin wrote:
> I'm starting to look at packaging zef to permit our users to install
> whatever module they want in their home directory.

Cool... I  started some work but never managed to get a proper solution. 

Here's what I did:
* used upstream repo and created package file in debian/sid branch
 following this method [1]
* created most of packages files

Then I stopped because zef is not the right tool to create debian package from 
perl6 module. But that should not stop you to provide zef to Debian users.

That said, I still have to figure out how to handle pre-compiled files in 
various upgrade scenario (rakudo upgrade, module upgrade) and removal.
See the long story on github [2]

> I used to create git repository for packaging named pkg-<project>.

is it already on alioth ?

> As far as I remember, we choose to name all perl6 packages with a
> “perl6-” prefix, like:
> - perl6-zef
> - perl6-meta6-bin

> So, I'm using the “pkg-perl6-” prefix to name the Git repositories, this
> permits me to distinguish from upstream repository.

This point becomes moot if method [1] is used, and I don't expect /git/pkg-
rakudo to contain anything else than perl6 package, so it may be redundant. 
Take also into account that you can choose any name for your local repo. Only 
git remote is important. Once the remote is set, you almost never deal with 
it. So I think the pkg- prefix on alioth repo is not useful. 

> What should we generalise as a naming scheme?

I'd rather not generalise this as a repo naming scheme on alioth. But that's 
not a strong opposition.

If you want, I can push what I have on alioth.. (but I reserve the right to 
choose the remote repo name ;-) )

All the best

--   -o-  -o-   irc: dod at

More information about the Pkg-rakudo-devel mailing list