[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

R: Re: Including Yampa



Hello, you need to become a Debian Maintainer only if you need to upload your package without a sponsor. If you want to look for a sponsor each time you want to upload to unstable a new revision, you don't need to declare anything...

But sponsorship process might take long time due to the lack of sponsors...

In any case if the package is good and you commit on git, you migh tfind somebody to sponsor just with a message on mail list.
Subscribing to debian haskell is appreciated or at least to your package bugs.

G.
(Sorry for top posting and lack of quality, I'm writing from mobile)

Inviato da Yahoo Mail su Android

Il Dom, 18 Nov, 2018 alle 13:31, Ivan Perez
<ivan.perez@keera.co.uk> ha scritto:
On 28/10/18 19:50, Mikolaj Konarski wrote:

>> I'd like to include Yampa in debian.
> Yay!
>
> I'm only a debian-haskell newbie, but this makes me still
> vaguely remember the location of some intro info.
>
> First, you will need to be a Debian maintainer or to somehow
> curry the goodwill of existing debian-haskell (busy) patrons
> to be able to upload the packages.
>
> Second, there are two repos of interest (ask for write access).
>
> Here you will create your package (which is not the same
> as uploading, the latter needs to be done by a Debian maintainer):
>
> https://salsa.debian.org/haskell-team/DHG_packages
>
> And here you will prove to the world, after checking locally,
> that uploading the package won't cause any disaster:
>
> https://salsa.debian.org/haskell-team/package-plan
>
> The docs in both repos are relatively up to date and there
> may be some other docs/tools of interest around there,
> though most are outdated (and I forgot which).
>
> Feel free to ask more questions. Generally, it's all doable,
> because I'm coping fine without even being a Debian maintainer
> (and without expending prohibitively many sweets to curry
> the said goodwill:).

>
Thanks!

I've been taking a look at this, how to become a debian maintainer,
reading the man page for DHG, etc.

The process of becoming a Debian Maintainer seems relatively time
consuming. There's a bureaucratic part (e.g., subscribing to lists,
lurking, announcing your intentions, finding a sponsor), and a technical
part (e.g., reading the Guide for Debian Maintainers, a 135-page PDF).

I've been looking around the DHG repo, and have seen that most packages
are relatively simple. I think I might even be able to create one from
scratch for Yampa (without additional tools, not that that is recommended).

Given the specific setup you have for haskell packages, I wonder how
much of both the bureaucratic and technical steps that generally apply
to debian haskell maintainers and haskell packages.

Should I be reading the Guide for Debian Maintainers if my purpose is to
add haskell packages (both libraries and executables) to Debian? If some
of the tools in DHG simplify the process of packaging and publishing,
what steps should I actually be following to package and publish a
haskell package?

Should i announce my intentions of packaging Yampa to some mailing list
other than this one? Or try to get a sponsor at debian-mentors?

All the best,

Ivan



Reply to: