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
Andreas Enge skribis:
> 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 patch in British English. Do we have a rule
> on which spelli
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
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 patch in British English. Do we have a rule
on which spelling to use? British is what I lear
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
Andreas Enge skribis:
> it looks like I have stumbled upon an enormous dependency tree:
>
> For kdelibs, I would like soprano;
> for soprano, I would like redland;
> for redland, I need rasqal;
> for some tests of rasqal to work, I need perl-xml-dom;
> for perl-xml-dom, I need libwww-perl;
> for
10 matches
Mail list logo
