Hi All,
I have a few packages at CPAN.
Recently, I created a package, Env::Assert <https://metacpan.org/dist/Env-Assert> which I used at the office when creating containers for data pipelines.
To make it easier to use Env::Assert in Debian containers, I would like to package it for Debian. But I know nothing about Debian packaging, besides,
of course, using them (installing with apt or dpkg).
Can anyone help me to package Env::Assert, please?
On 31 Oct 2023, at 01:21, gregor herrmann <[email protected]> wrote:
On Sat, 28 Oct 2023 10:56:46 +0200, Mikko Johannes Koivunalho wrote:
Hi All,
Hi Mikko!
I have a few packages at CPAN.
Recently, I created a package, Env::Assert
<https://metacpan.org/dist/Env-Assert> which I used at the office when
creating containers for data pipelines.
Alright :)
To make it easier to use Env::Assert in Debian containers, I would like to >> package it for Debian. But I know nothing about Debian packaging, besides, >> of course, using them (installing with apt or dpkg).
Can anyone help me to package Env::Assert, please?
I think the question is: What is your objective?
- If you want to learn creating Debian packages and join the Debian
Perl Group and maintain 4000 packages -- great, we need more
people!
- If you want to get Env::Assert into Debian, the easiest way is to
ask us to package it :)
If it's the latter: I just spent 2 minutes with dh-make-perl and
Env::Assert, and if I spend 5 minutes more, I can upload the package
to the archive. [0]
If it's the former: Additionally to Andrius' hints we can give you
more pointers for getting into the packaging business.
Cheers,
gregor
[0] Although I just realize that this might be better named envassert
than libenv-assert-perl, as it's more about the binary than the
library, right?
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
Hi Gregor,
On 31 Oct 2023, at 01:21, gregor herrmann <[email protected]> wrote:Yes, please!
On Sat, 28 Oct 2023 10:56:46 +0200, Mikko Johannes Koivunalho wrote:
Hi All,Hi Mikko!
I have a few packages at CPAN.Alright :)
Recently, I created a package, Env::Assert
<https://metacpan.org/dist/Env-Assert> which I used at the office when
creating containers for data pipelines.
To make it easier to use Env::Assert in Debian containers, I would like to >>> package it for Debian. But I know nothing about Debian packaging, besides, >>> of course, using them (installing with apt or dpkg).I think the question is: What is your objective?
Can anyone help me to package Env::Assert, please?
- If you want to learn creating Debian packages and join the Debian
Perl Group and maintain 4000 packages -- great, we need more
people!
- If you want to get Env::Assert into Debian, the easiest way is to
ask us to package it :)
Thank you.
If it's the latter: I just spent 2 minutes with dh-make-perl andHave I done everything right so the packaging is as easy as possible?
Env::Assert, and if I spend 5 minutes more, I can upload the package
to the archive. [0]
Just tell me if there is anything missing.
If it's the former: Additionally to Andrius' hints we can give youYes, that’s right. In this case the library is mostly a bi-product, not really meant to be used by itself.
more pointers for getting into the packaging business.
Cheers,
gregor
[0] Although I just realize that this might be better named envassert
than libenv-assert-perl, as it's more about the binary than the
library, right?
Would it be better if Env::Assert was two separate (CPAN) packages, one for lib and one for executable?
Thank you.
Sincerely,
Mikko Koivunalho
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
- If you want to get Env::Assert into Debian, the easiest way is toYes, please!
ask us to package it :)
Thank you.
If it's the latter: I just spent 2 minutes with dh-make-perl and Env::Assert, and if I spend 5 minutes more, I can upload the packageHave I done everything right so the packaging is as easy as possible?
to the archive. [0]
Just tell me if there is anything missing.
[0] Although I just realize that this might be better named envassertYes, that’s right. In this case the library is mostly a bi-product,
than libenv-assert-perl, as it's more about the binary than the
library, right?
not really meant to be used by itself.
Would it be better if Env::Assert was two separate (CPAN) packages,
one for lib and one for executable?
Sorry for hijacking this thread, but can I please request a new package too?
App::Session::Token / https://metacpan.org/dist/App-Session-Token/view/bin/session-token
This is a command-line interface for my Session::Token library (already packaged as libsession-token-perl).
For my everyday work-flow, it's the only package I still need to install
from CPAN. I also think it would be useful for other people. If I had to suggest a package name I'd say just "session-token" (name of the bin) but anything would be fine.
Actually I tried to figure out how to do the packaging myself a while ago, but something wasn't working for me (a form URL was timing out IIRC) so I gave up.
In case it helps, I made a wish-list description:
You could have started a new thread, it's not that we we have a limit
on threads on our mailing lists :)
Actually I tried to figure out how to do the packaging myself a while ago, >> but something wasn't working for me (a form URL was timing out IIRC) so ISounds, hm, interesting :)
gave up.
(We can't -- technically and by policy -- use online resources during
build.)
One thing I'm wondering is why App::Session::Token is distributedYes, this could work too. Initially I thought to keep them separate,
separately from Session::Token; no big deal for us to have Yet
Another Package but putting a script into the distribution with the
library seems to be quite common.
On 10/31/23 22:13, gregor herrmann wrote:
You could have started a new thread, it's not that we we have a limitHaha good point -- I just saw your offer to help with Mikko's package and jumped at it. My mistake. :)
on threads on our mailing lists :)
One thing I'm wondering is why App::Session::Token is distributed separately from Session::Token; no big deal for us to have YetYes, this could work too. Initially I thought to keep them separate,
Another Package but putting a script into the distribution with the
library seems to be quite common.
thinking some users of the library would not want to also install a script. And at this point, the library is pretty widely used so I'm hesitant to push a script onto all installations.
On Tue, 31 Oct 2023 09:26:09 +0100, Mikko Koivunalho wrote:
Alright, let's take this route :)- If you want to get Env::Assert into Debian, the easiest way is toYes, please!
ask us to package it :)
Thank you.
I haven't noticed anything yesterday in my 2-minute-check but thanksIf it's the latter: I just spent 2 minutes with dh-make-perl andHave I done everything right so the packaging is as easy as possible?
Env::Assert, and if I spend 5 minutes more, I can upload the package
to the archive. [0]
Just tell me if there is anything missing.
for the offer!
Ok, thanks for the confirmation.[0] Although I just realize that this might be better named envassertYes, that’s right. In this case the library is mostly a bi-product,
than libenv-assert-perl, as it's more about the binary than the
library, right?
not really meant to be used by itself.
Would it be better if Env::Assert was two separate (CPAN) packages,I think that would be overkill.
one for lib and one for executable?
What I often see is that distributions like this are named App-foo on
the CPAN, so maybe App-envassert would be an option. But from a
Debian point of view that's irrelevant …
Cheers,
gregor
One thing I'm wondering is why App::Session::Token is distributed separately from Session::Token; no big deal for us to have YetYes, this could work too. Initially I thought to keep them separate, thinking some users of the library would not want to also install a
Another Package but putting a script into the distribution with the
library seems to be quite common.
script. And at this point, the library is pretty widely used so I'm
hesitant to push a script onto all installations.
On Wed, 2023-11-01 at 14:04 -0400, Doug Hoyte wrote:
Given the script is about 3600 kB (bin and module), I don't think manyOne thing I'm wondering is why App::Session::Token is distributedYes, this could work too. Initially I thought to keep them separate,
separately from Session::Token; no big deal for us to have Yet
Another Package but putting a script into the distribution with the
library seems to be quite common.
thinking some users of the library would not want to also install a
script. And at this point, the library is pretty widely used so I'm
hesitant to push a script onto all installations.
people would notice it. ;) It could be an optional install.
Cheers,
Andrew
Probably you are right. If you all feel this is the best way I can do
this instead. Please let me know.
Cheers,
Doug
On 11/1/23 17:01, Andrew Ruthven wrote:
On Wed, 2023-11-01 at 14:04 -0400, Doug Hoyte wrote:
Given the script is about 3600 kB (bin and module), I don't think many people would notice it. ;) It could be an optional install.One thing I'm wondering is why App::Session::Token is distributed separately from Session::Token; no big deal for us to have YetYes, this could work too. Initially I thought to keep them separate, thinking some users of the library would not want to also install a script. And at this point, the library is pretty widely used so I'm hesitant to push a script onto all installations.
Another Package but putting a script into the distribution with the library seems to be quite common.
Cheers,
Andrew
When Env:Assert is packaged, will it become available to all supported Debians? When?
Is there a repository for the packaging code?
Oh, and looking at this now I see I was a unit out. It is ~3.6 kB. :)
[Could y'all please stop top-posting? This makes replying/quoting
quite hard …]
What's the status here?
Doug, have you decided if you want to merge App::Session::Token into Session::Token?
What's the status here?Personally I would prefer a separate package, just because I don't really know if there are any down-stream consequences for anyone who depends on the CPAN distribution or deb/rpm packages. This is how it's been distributed for [checks notes] 11 years -- now I feel old! :)
Doug, have you decided if you want to merge App::Session::Token into Session::Token?
On Sun, 12 Nov 2023 08:08:20 -0500, Doug Hoyte wrote:
session-token_0.102-1 uploaded to the new queue, sorry for the delay.What's the status here?Personally I would prefer a separate package, just because I don't really
Doug, have you decided if you want to merge App::Session::Token into
Session::Token?
know if there are any down-stream consequences for anyone who depends on the >> CPAN distribution or deb/rpm packages. This is how it's been distributed for >> [checks notes] 11 years -- now I feel old! :)
Cheers,
gregor
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 28:22:10 |
| Calls: | 12,107 |
| Calls today: | 7 |
| Files: | 15,006 |
| Messages: | 6,518,231 |