[PATCH] gnu: Add GNU acct.

[Nikita Karetnikov]

May I push this patch?

From 20809203713f119ffaa0fb6d372b73cce5d1cf51 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov 
Date: Thu, 10 Oct 2013 10:32:15 +
Subject: [PATCH] gnu: Add GNU acct.

* gnu/packages/acct.scm: New file.
* gnu-system.am (GNU_SYSTEM_MODULES): Add it.
---
 gnu-system.am |1 +
 gnu/packages/acct.scm |   44 
 2 files changed, 45 insertions(+)
 create mode 100644 gnu/packages/acct.scm

diff --git a/gnu-system.am b/gnu-system.am
index 37a174c..0132187 100644
--- a/gnu-system.am
+++ b/gnu-system.am
@@ -22,6 +22,7 @@
 
 GNU_SYSTEM_MODULES =\
   gnu/packages.scm\
+  gnu/packages/acct.scm\
   gnu/packages/acl.scm\
   gnu/packages/algebra.scm			\
   gnu/packages/apr.scm\
diff --git a/gnu/packages/acct.scm b/gnu/packages/acct.scm
new file mode 100644
index 000..e892fd8
--- /dev/null
+++ b/gnu/packages/acct.scm
@@ -0,0 +1,44 @@
+;;; GNU Guix --- Functional package management for GNU
+;;; Copyright © 2013 Nikita Karetnikov 
+;;;
+;;; This file is part of GNU Guix.
+;;;
+;;; GNU Guix is free software; you can redistribute it and/or modify it
+;;; under the terms of the GNU General Public License as published by
+;;; the Free Software Foundation; either version 3 of the License, or (at
+;;; your option) any later version.
+;;;
+;;; GNU Guix is distributed in the hope that it will be useful, but
+;;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;;; GNU General Public License for more details.
+;;;
+;;; You should have received a copy of the GNU General Public License
+;;; along with GNU Guix.  If not, see .
+
+(define-module (gnu packages acct)
+  #:use-module (guix licenses)
+  #:use-module (guix packages)
+  #:use-module (guix download)
+  #:use-module (guix build-system gnu))
+
+(define-public acct
+  (package
+(name "acct")
+(version "6.6.1")
+(source
+ (origin
+  (method url-fetch)
+  (uri (string-append "mirror://gnu/acct/acct-"
+  version ".tar.gz"))
+  (sha256
+   (base32
+"1jzz601cavml7894fjalw661gz28ia35002inw990agr3rhiaiam"
+(build-system gnu-build-system)
+(home-page "https://gnu.org/software/acct/";)
+(synopsis "Standard login and process accounting utilities")
+(description
+ "GNU acct provides a means for system administrators to determine
+system usage patterns.  It provides information on, for example, connections,
+programs executed, and system resources used.")
+(license gpl3+)))
-- 
1.7.9.5



pgpI7o0UdziSA.pgp
Description: PGP signature

Re: a2ps: manpages fail to build

[Nikita Karetnikov]

> It invokes /missing instead of $top_srcdir/build-aux/missing.

>> I added ‘help2man’, but it didn’t help.

> Could you check the configure log for clues?

> Also, can you check the makefiles to see how it’s supposed to build the
> man pages?

It just needed Perl.

>>> Rather use (substitute* (find-files "." ".*") ...) if that works.

> Too much time?  But it succeeds?

Sorry, I was thinking about a different command.  Yours fails with
“string contains #\nul character.”  May I stick to the list of files
instead of using ‘find-files’?

Now, 20 of 25 tests failed.  Tests are written in Ksh, not Bash, so I’ll
try to package it first.


pgpeqdpNkxvF0.pgp
Description: PGP signature

Re: [PATCH] gnu: Add GNU acct.

[Ludovic Courtès]

Nikita Karetnikov  skribis:

> May I push this patch?
>
>
> From 20809203713f119ffaa0fb6d372b73cce5d1cf51 Mon Sep 17 00:00:00 2001
> From: Nikita Karetnikov 
> Date: Thu, 10 Oct 2013 10:32:15 +
> Subject: [PATCH] gnu: Add GNU acct.
>
> * gnu/packages/acct.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.

Yes, please!  (Make sure ‘make sync-descriptions’ doesn’t complain.)

Ludo’.

Re: Brasero, or gnome without gnome

[Ludovic Courtès]

Aljosha Papsch  skribis:

> Am Mittwoch, den 09.10.2013, 22:22 +0200 schrieb Ludovic Courtès:
>> I think we can follow our personal preferences to start with (I got
>> Guile, Emacs, and Ratpoison because that’s pretty much all I
>> need ;-)).
>> We do want to support some of these fancy desktops, but I don’t think
>> there’s much we can plan: if/when someone wants to add XFCE, KDE, or
>> Enlightenment, they’ll do it.
>
> I was trying to propose that Guix uses XFCE as the base for GNOME
> (maybe: XFCE/GNOME) for the long term, assuming that non-systemd GNOME
> installs won't be able to use gdm and some core functionality anymore in
> the future.

Ah OK.  “As the base for GNOME” means that the desktop thing would be
XFCE, but the applications would be from GNOME, right?  That’s probably
a good workaround for the likely systemd-only future of GNOME.

>> Work on adding GNUstep and GNOME is very welcome as these are the
>> preferred desktops in the GNU system.  Perhaps we should look for
>> hackers in these projects to give a hand.
>
> At the moment it should be doable to package GNOME as it is.  I was only
> referring to the future.  Just trying to plan, at least a little :)

OK, understood.  :-)

Ludo’.

Re: a2ps: manpages fail to build

[Ludovic Courtès]

Nikita Karetnikov  skribis:

>> It invokes /missing instead of $top_srcdir/build-aux/missing.
>
>>> I added ‘help2man’, but it didn’t help.
>
>> Could you check the configure log for clues?
>
>> Also, can you check the makefiles to see how it’s supposed to build the
>> man pages?
>
> It just needed Perl.

OK.

 Rather use (substitute* (find-files "." ".*") ...) if that works.
>
>> Too much time?  But it succeeds?
>
> Sorry, I was thinking about a different command.  Yours fails with
> “string contains #\nul character.”  May I stick to the list of files
> instead of using ‘find-files’?

Hmm yes, but it looks really long, and thus hard to maintain.  Can’t it
be reduced?

> Now, 20 of 25 tests failed.  Tests are written in Ksh, not Bash, so I’ll
> try to package it first.

Forgive my ignorance, but is Ksh somehow compatible with tcsh (tcsh is
already packaged)?

Thanks,
Ludo’.

Re: Brasero, or gnome without gnome

[Andreas Enge]

On Wed, Oct 09, 2013 at 07:03:09PM +0200, Aljosha Papsch wrote:
> The question is which gnome applications.  My personal priority list
> would be:

I think this is exactly the way to go, package the applications you are
interested in (with the added bonus that they will be tested in a real
environment).

Andreas

Re: Qt

[Andreas Enge]

On Tue, Oct 08, 2013 at 11:05:04PM +0200, Ludovic Courtès wrote:
> Andreas Enge  skribis:
> > Also, the build uses
> > sse/sse2/... instructions according to what is available on the
> > processor; we might wish to disable all or at least the most advanced
> > of them in the long run.
> If it’s a matter of adding the right configure flag, I’d do it before
> it bites.

The following will leave out any special instructions, as far as I can see:
+  "-no-sse2"
+  "-no-sse3"
+  "-no-ssse3"
+  "-no-sse4.1"
+  "-no-sse4.2"
+  "-no-avx"
+  "-no-avx2"
+  "-no-neon"
+  "-no-mips_dsp"
+  "-no-mips_dspr2"

I do not know how much this slows down qt applications. According to wikipedia,
sse2 arrived in 2001. So one could argue that adding it would exclude almost
no machines.

Andreas

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

[Nikita Karetnikov]

>>> Sorry, I don't understand what problem you're trying to solve.
>>> Why are you separating copyright text and license text?  

I don’t know how to keep the @ifinfo trick (see the attachment) without
separating them.  Maybe the @ifinfo part should be removed.

>>> Can you send me the whole file (beginning of it, anyway)?
>>> The diff is hard to read.

Attached.

>> And yeah, there could be a single macro since the two always go
>> together.

> Why is a macro needed at all?
> (vs. just using text inside @copying).

In the document, nearly the same (more on that later) copyright notice
is repeated three times.  A new contributor would have to adjust each
notice, which is error-prone.

Now, I said “nearly” because the “Copyright” lines are different, but
they should be identical.

\input texinfo
@c -*-texinfo-*-

@c %**start of header
@setfilename guix.info
@documentencoding UTF-8
@settitle GNU Guix Reference Manual
@c %**end of header

@include version.texi
@set YEARS 2012, 2013

@dircategory Package management
@direntry
* guix: (guix).   Guix, the functional package manager.
* guix package: (guix)Invoking guix package
  Managing packages with Guix.
* guix build: (guix)Invoking guix build
  Building packages with Guix.
@end direntry

@titlepage
@title GNU Guix Reference Manual
@subtitle Using the GNU Guix Functional Package Manager
@author Ludovic Courtès
@author Andreas Enge
@author Nikita Karetnikov

@page
@vskip 0pt plus 1filll
Edition @value{EDITION} @*
@value{UPDATED} @*

Copyright @copyright{} @value{YEARS} Ludovic Court@`es, Andreas Enge, Nikita 
Karetnikov

@ifinfo
@quotation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
copy of the license is included in the section entitled ``GNU Free
Documentation License''.
@end quotation
@end ifinfo

@end titlepage

@copying
This manual documents GNU Guix version @value{VERSION}.

Copyright @copyright{} @value{YEARS} Ludovic Courtès

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
copy of the license is included in the section entitled ``GNU Free
Documentation License.''
@end copying

@contents

@c *
@node Top
@top GNU Guix

This document describes GNU Guix version @value{VERSION}, a functional
package management tool written for the GNU system.


@quotation
Copyright @copyright{} @value{YEARS} Ludovic Courtès, Andreas Enge, Nikita 
Karetnikov

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
copy of the license is included in the section entitled ``GNU Free
Documentation License.''
@end quotation


pgpcBeSFTlxGX.pgp
Description: PGP signature

Re: Qt

[Ludovic Courtès]

Andreas Enge  skribis:

> On Tue, Oct 08, 2013 at 11:05:04PM +0200, Ludovic Courtès wrote:
>> Andreas Enge  skribis:
>> > Also, the build uses
>> > sse/sse2/... instructions according to what is available on the
>> > processor; we might wish to disable all or at least the most advanced
>> > of them in the long run.
>> If it’s a matter of adding the right configure flag, I’d do it before
>> it bites.
>
> The following will leave out any special instructions, as far as I can see:
> +  "-no-sse2"
> +  "-no-sse3"
> +  "-no-ssse3"
> +  "-no-sse4.1"
> +  "-no-sse4.2"
> +  "-no-avx"
> +  "-no-avx2"
> +  "-no-neon"
> +  "-no-mips_dsp"
> +  "-no-mips_dspr2"
>
> I do not know how much this slows down qt applications. According to 
> wikipedia,
> sse2 arrived in 2001. So one could argue that adding it would exclude almost
> no machines.

Yes, you may be right for SSE2 (especially considering the fact that
this kind of software is typically used on fairly recent machines.)

Ludo’.

Re: Qt

[Andreas Enge]

On Thu, Oct 10, 2013 at 03:09:09PM +0200, Ludovic Courtès wrote:
> Andreas Enge  skribis:
> > I do not know how much this slows down qt applications. According to 
> > wikipedia,
> > sse2 arrived in 2001. So one could argue that adding it would exclude almost
> > no machines.
> Yes, you may be right for SSE2 (especially considering the fact that
> this kind of software is typically used on fairly recent machines.)

Finally, I disabled everything special. As this is not a number crunching
library, I would like to be convinced of the usefulness of SSE.

Andreas

LXDE, was: Brasero, or gnome without gnome

[Andreas Enge]

On the desktop front, I just came across this on my search for a simple
sample qt application to check my library with:
   
http://www.zdnet.com/lxde-waves-goodbye-to-gtk-in-merge-with-razor-qt-718476/

Andreas

Re: Treating patches as part of ‘origin’

[Ludovic Courtès]

l...@gnu.org (Ludovic Courtès) skribis:

> There’s still work in that area: in ‘core-updates’, I’ll remove the
> ‘patch’ phase and #:patches argument from ‘gnu-build-system’ & co., and
> update the core packages that still use #:patches.

I’ve reopened the ‘core-updates’ branch and made those changes, so
#:patches is no more!

Ludo’.

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

[Karl Berry]

I donœôòùt know how to keep the @ifinfo trick

I see no need for @ifinfo.  It has no effect inside @titlepage anyway,
since @titlepage ... @end titlepage is ignored for Info output.

nearly the same (more on that later) copyright notice
is repeated three times.

1) @copying should come first.

2) @insertcopying can/should be used to insert the copying text in
@titlepage and anywhere else.  I created @insertcopying at the same time
as @copying, precisely to avoid having to write the copying text more
than once.

3) I see no need for @macro.  I also don't think a YEARS variable makes
sense.  The years will be different for different people.

4) I see no need for a separate EDITION and UPDATED in the
@titlepage text, but whatever.

5) The period outside the quotes in the standard text is intentional
(per fdl.texi).  Not that it's the end of the world to have it inside.

6) All this is shown in the "short example" document that is in the
Texinfo manual.  

Appended is another version of your frontmatter this way.  (Probably
with the accented characters messed up, but you get the idea.)

BTW, rms prefers that the Top node not include @insertcopying, but it's
up to you.  (I see I haven't taken @insertcopying out of the Top node
in the Texinfo manual's example document.  Oops.)

BTW 2, the spaces in your "guix package" and "guix build" dir entries 
make completion painful.  Also you're missing periods after the node
names.  Also the dir file is much more readable if entries are kept on
one line at all costs.  I suggest:
@direntry
* Guix (guix).  Guix, the functional package manager.
* guix-package (guix)Invoking guix package.  Managing packages with Guix.
* guix-build (guix)Invoking guix build.  Building packages with Guix.
@end direntry

Ok, that's more than enough for one message ...

Best,
karl


\input texinfo
@c -*-texinfo-*-

@c %**start of header
@setfilename guix.info
@documentencoding UTF-8
@settitle GNU Guix Reference Manual
@c %**end of header

@include version.texi
@set YEARS 2012, 2013

@copying
This manual documents GNU Guix version @value{VERSION}.

Copyright @copyright{} @value{YEARS} Ludovic Courtès

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
copy of the license is included in the section entitled ``GNU Free
Documentation License.''
@end copying

@dircategory Package management
@direntry
* guix: (guix).   Guix, the functional package manager.
* guix package: (guix)Invoking guix package
  Managing packages with Guix.
* guix build: (guix)Invoking guix build
  Building packages with Guix.
@end direntry

@titlepage
@title GNU Guix Reference Manual
@subtitle Using the GNU Guix Functional Package Manager
@author Ludovic Courtès
@author Andreas Enge
@author Nikita Karetnikov

@page
@vskip 0pt plus 1filll
Edition @value{EDITION} @*
@value{UPDATED} @*

@insertcopying
@end titlepage

@contents

@c *
@node Top
@top GNU Guix

This document describes GNU Guix version @value{VERSION}, a functional
package management tool written for the GNU system.

@insertcopying

Re: Qt

[Mark H Weaver]

Andreas Enge  writes:

> On Thu, Oct 10, 2013 at 03:09:09PM +0200, Ludovic Courtès wrote:
>> Andreas Enge  skribis:
>> > I do not know how much this slows down qt applications. According to 
>> > wikipedia,
>> > sse2 arrived in 2001. So one could argue that adding it would exclude 
>> > almost
>> > no machines.
>> Yes, you may be right for SSE2 (especially considering the fact that
>> this kind of software is typically used on fairly recent machines.)
>
> Finally, I disabled everything special.

You can assume SSE2 on x86_64, as _all_ x86_64 processors have it.  In
fact, the C function calling conventions of SysV x86_64 psABI (used by
GNU/Linux) specify that the SSE2 registers are used for passing floating
point values as arguments.

> As this is not a number crunching library, I would like to be
> convinced of the usefulness of SSE.

Qt is not a number crunching library, but I suspect it _does_ have image
rendering code, where SIMD instruction sets such as SSE2 can make a
dramatic difference in performance.

Regards,
  Mark