least since 1994-10-17 (see the README history
[1]
> What I understand is: when the License of Perl 5
There is no "License of Perl 5", it is Perl 5 that is dual licensed
The same dual license scheme is usually (usually?!?) adopted by Perl
modules, at least those on CPAN
http://www
Cyril Roelandt writes:
> On 12/23/2015 11:53 AM, Ricardo Wurmus wrote:
>> (I’ll try to set up git send-email soon.)
>>
> Seems ok, except for this:
>
> gnu/packages/perl.scm:5946:5: perl-unicode-linebreak-2015.12: sentences
> in description should be followed by two spaces; possible infraction
On 12/23/2015 11:53 AM, Ricardo Wurmus wrote:
> (I’ll try to set up git send-email soon.)
>
Seems ok, except for this:
gnu/packages/perl.scm:5946:5: perl-unicode-linebreak-2015.12: sentences
in description should be followed by two spaces; possible infraction at 104
Cyril.
(I’ll try to set up git send-email soon.)
>From d4f5da65aaa55df2880b3a1aac7705973e5ae272 Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus
Date: Tue, 22 Dec 2015 14:08:41 +0100
Subject: [PATCH 01/13] gnu: Add MIME::Charset.
* gnu/packages/perl.scm (perl-mime-charset): New variable.
---
gnu/packages
Fixed in 3a09e1d, which will be in 0.8.
Ludo’.
Andreas Enge skribis:
> On Sun, May 11, 2014 at 01:31:12PM +0200, Ludovic Courtès wrote:
>> But there’s no tool that really “interprets” of what’s in the
>> ‘description’ field[*]. What do you mean?
>> [*] Actually, ‘fill-paragraph’ from (guix ui), which is used for the
>> output of ‘guix pa
On Sun, May 11, 2014 at 01:31:12PM +0200, Ludovic Courtès wrote:
> But there’s no tool that really “interprets” of what’s in the
> ‘description’ field[*]. What do you mean?
> [*] Actually, ‘fill-paragraph’ from (guix ui), which is used for the
> output of ‘guix package --search’ does some very
Andreas Enge skribis:
> Thanks for the comments, all implemented and pushed.
Thanks!
> On Sun, May 11, 2014 at 11:54:02AM +0200, Ludovic Courtès wrote:
>> Also, two spaces after end-of-sentence periods.
>
> Just as a side note (side-note? sidenote?), in texinfo an end of sentence
> period immed
Thanks for the comments, all implemented and pushed.
On Sun, May 11, 2014 at 11:54:02AM +0200, Ludovic Courtès wrote:
> Also, two spaces after end-of-sentence periods.
Just as a side note (side-note? sidenote?), in texinfo an end of sentence
period immediately followed by a line break is interpre
s,
> unless these are already part of the official project name. But see
> -@ref{Python Modules} for special rules concerning modules for
> -the Python language.
> +@ref{Python Modules} and @ref{Perl Modules} for special rules concerning
> +modules for the Python and Perl languages.
Shou
On Sun, May 11, 2014 at 11:20:33AM +0200, John Darrington wrote:
> On Sun, May 11, 2014 at 10:56:38AM +0200, Andreas Enge wrote:
> (I feel like starting a bikeshed discussion ;-).)
> whichever, "bike shed" is two words.
Ah, a German mistake!
Andreas
On Sun, May 11, 2014 at 10:56:38AM +0200, Andreas Enge wrote:
On Sat, Dec 07, 2013 at 09:24:42PM +0100, Andreas Enge wrote:
> All very reasonable. Let us go for this (and I should add a section to
the
> packaging guidelines later on).
Months later, here is a proposed patc
what I learnt at school.
(I feel like starting a bikeshed discussion ;-).)
Andreas
>From 97a3ac573edcb3046ee9655497a97bdf750090ee Mon Sep 17 00:00:00 2001
From: Andreas Enge
Date: Sun, 11 May 2014 10:43:51 +0200
Subject: [PATCH] doc: Add a section on perl modules in the packaging
guideline
On Fri, Dec 06, 2013 at 11:56:17PM +0100, Ludovic Courtès wrote:
> I would add the ‘perl-’ prefix, unless the package stands alone (for
> instance, Hydra would be called ‘hydra’, not ‘perl-hydra’.)
Yes, that would be as for python.
> For the rest of the name, I would take the Perl module name. S
ed libwww-perl;
> for libwww-perl, I need a lot of packages:
Ouch. :-)
> This leads me to the question: How should the packages containing perl
> modules be named, and in which files should they be defined?
>
> So far, there are the following packages in xml.scm:
> perl-xml-
packages containing perl
modules be named, and in which files should they be defined?
So far, there are the following packages in xml.scm:
perl-xml-parser containing XML-Parser
perl-xml-parser-perlsax containing libxml-perl
perl-xml-simple containing XML-Simple
The second one is definitely a misnomer; I
16 matches
Mail list logo
