all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marek Benc <merkur32@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add nvi
Date: Tue, 02 Sep 2014 14:29:33 +0200	[thread overview]
Message-ID: <874mwqnr2q.fsf@gnu.org> (raw)
In-Reply-To: <540594E3.10008@gmail.com> (Marek Benc's message of "Tue, 02 Sep 2014 11:58:59 +0200")

Marek Benc <merkur32@gmail.com> skribis:

> On 09/02/2014 10:19 AM, Ludovic Courtès wrote:

[...]

>> Shouldn’t it be
>> https://sites.google.com/a/bostic.com/keithbostic/files/... ?  (This is
>> the URL given on the home page.)
> Actually, no. The actual home page, according to Debain, is
> http://www.kotnet.org/~skimo/nvi/ ; However, that site is dead. I've
> looked at what other distributions report and they say
> https://sites.google.com/a/bostic.com/keithbostic/vi is currently the
> home of nvi. Unfortunately, they don't provide the latest version of
> the editor (there's even a bug in the build system of that version),
> so I had to look somewhere else to get the newest one, which I found
> at Slackbuilds and some other places, like the Debian source
> repository.

In that case please leave the sites.google.com home page, with a comment
above the source URL stating that sites.google.com is stale etc.

> I think I'll remove the website from the definition, as it'll cause
> confusion (It confused even me).
>>> +    (license bsd-3)))
>> This is actually bsd-4 (see its ‘LICENSE’ file: it has the four clauses,
>> as shown at <http://directory.fsf.org/wiki/License:BSD_4Clause>.)
> Really? I see there only 3 clauses, here's a listing of the LICENSE file:

I was looking at nvi-1.79/LICENSE and nvi-1.79/regex/COPYRIGHT, which
both contain the 4-clause text.  It’s surprising that the newer version
no longer has the fourth clause.

Which version do Trisquel or Debian ship?  What does their ‘copyright’
file says?

> Okay, now that that's out of the way, here's the updated patch:
>
> 2014-09-02  Marek Benc  <merkur32@gmail.com>

For the subject line, use “gnu: Add nvi.”

> * gnu/packages/nvi.scm: Add the nvi editor.
> * gnu/packages/patches/nvi-assume-preserve-path.patch: Assume nvi can
> store backups in /var/tmp.

In both cases, “New file.” is enough (try ‘git log’ to see examples.)

The files also need to be added to gnu-system.am.

Could you send the patch (with the added comments) as an attachment,
because the mail client apparently mangled it?

Thanks,
Ludo’.

  reply	other threads:[~2014-09-02 12:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 13:33 [PATCH] Add nvi Marek Benc
2014-09-02  8:19 ` Ludovic Courtès
2014-09-02  9:58   ` Marek Benc
2014-09-02 12:29     ` Ludovic Courtès [this message]
2014-09-02 13:25       ` Marek Benc
2014-09-02 19:36         ` Ludovic Courtès
2014-09-02 10:09 ` Cyril Roelandt
2014-09-02 10:18   ` Taylan Ulrich Bayirli/Kammer
2014-09-02 12:21     ` Ludovic Courtès
2014-09-02 12:18   ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=874mwqnr2q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=merkur32@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.