From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@yhbt.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 6F63D1F5AE;
	Thu,  9 Jul 2020 20:15:07 +0000 (UTC)
Date: Thu, 9 Jul 2020 20:15:07 +0000
From: Eric Wong <e@yhbt.net>
To: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= <ukleinek@debian.org>,
	964736@bugs.debian.org
Cc: meta@public-inbox.org
Subject: Re: Bug#964736: ITP: public-inbox -- Mailing list archiver
Message-ID: <20200709201507.GA26225@dcvr>
References: <159431280208.6933.12275160953943132869.reportbug@taurus.defre.kleine-koenig.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <159431280208.6933.12275160953943132869.reportbug@taurus.defre.kleine-koenig.org>
List-Id: <meta.public-inbox.org>

Uwe Kleine-König <ukleinek@debian.org> wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Uwe Kleine-König <ukleinek@debian.org>
> 
> * Package name    : public-inbox
>   Version         : 1.5.0
>   Upstream Author : Eric Wong <e@yhbt.net> and others
> * URL             : https://www.public-inbox.org/
> * License         : AGPL-3.0
>   Programming Lang: Perl
>   Description     : versatile mailing (list) archiver
> 
> This software powers https://lore.kernel.org/ and also
> http://www.public-inbox.org/ itself. It's the server-side counter part

+Cc: meta@public-inbox.org

Probably better to list https://public-inbox.org/hosted.html
instead of its "homepage" as an example.  Also, no need for
"www.", URLs with Message-IDs are long enough as they are and
I'm unlikely to ever to want multiple IPs/hosts behind
public-inbox.org.

> for b4 that is already packaged in Debian.
> 
> Currently I evaluate it to provide an archive for several work related
> mailing lists.
> 
> Depending on the outcome of this evaluation I might or might not actually
> package public-inbox. But as deploying is easy using debian packages I
> will create at least simple packaging which should at a minimum give a
> good start for someone to pick up from me.

Great to hear.  I'm somewhat familiar with Debian packaging and
debhelper, so I can help.

Fwiw, I've been thinking about providing "make deb-pkg" and
"make bindeb-pkg" targets (identical to what Linux kernel
provides) for end users to build their own packages, too.  It
would be non-intrusive to distro packagers (no "debian/"
directory in VCS).