user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Eric Wong <e@yhbt.net>, 964736@bugs.debian.org
Cc: meta@public-inbox.org
Subject: Re: Bug#964736: ITP: public-inbox -- Mailing list archiver
Date: Thu, 9 Jul 2020 22:51:11 +0200	[thread overview]
Message-ID: <5bcd1b23-11d4-ea0c-5629-875711b9e474@debian.org> (raw)
In-Reply-To: <20200709201507.GA26225@dcvr>

Hello Eric,

On 7/9/20 10:15 PM, Eric Wong wrote:
> 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

The original mail should have been Cc:d already to there.

> Probably better to list https://public-inbox.org/hosted.html

noted.

> 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.

I don't feel strong here. I doubt that the homepage field will be used
to create a Message-Id-Link from it.

>> 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.

I already have a prototype at
https://salsa.debian.org/ukleinek/public-inbox

If you want to take a look ... I'm nearly sure the list of dependencies
is incomplete.

> 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).

Here I also don't care much, I'd use the official package :-)

Thanks for your feedback
Uwe

      reply	other threads:[~2020-07-09 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 16:40 Bug#964736: ITP: public-inbox -- Mailing list archiver Uwe Kleine-König
2020-07-09 20:15 ` Eric Wong
2020-07-09 20:51   ` Uwe Kleine-König [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bcd1b23-11d4-ea0c-5629-875711b9e474@debian.org \
    --to=ukleinek@debian.org \
    --cc=964736@bugs.debian.org \
    --cc=e@yhbt.net \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).