all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Acl
Date: Wed, 05 Nov 2014 21:38:32 +0100	[thread overview]
Message-ID: <87sihx1iyf.fsf@gnu.org> (raw)
In-Reply-To: <20141105193513.GA30433@debian> (Andreas Enge's message of "Wed, 5 Nov 2014 20:35:13 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> Adding optional inputs to kdelibs, I notice that acl is not recognised.
> The reason is that the header files are not installed. Would that be easy
> to modify? Maybe by changing the line
>   (zero? (system* "make" "install" "install-lib")))

Commit 16755848 added ‘install-lib’ (before that libacl.so was not
installed), but yeah, installing headers would have been cool too.  ;-)

> to
>   (zero? (system* "make" "install")))
> or not replacing the normal install phase (but then there may be a
> reason for this special command!).

ISTR that the ‘install’ target installs only the executables.

> Concerning the acl test failures, I tried
>  #:tests? #t
> and found that there is no "check" target. A good reason for the
> tests to fail...

Heh.

Anyway, this is depended on by Coreutils, so changes should go to
core-updates.

In the meantime, you can always add a fixed version of ACL for use in
KDE (you could even add a ‘replacement’ field pointing to it in ‘acl’
itself, although that doesn’t seem like a very good use case.)

Thanks for looking into it!

Ludo’.

  reply	other threads:[~2014-11-05 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 19:35 Acl Andreas Enge
2014-11-05 20:38 ` Ludovic Courtès [this message]
2014-11-06 21:38   ` Acl Andreas Enge
2014-11-06 22:09     ` Acl Andreas Enge
2014-11-07  9:15       ` Acl Ludovic Courtès
2014-11-07 22:30         ` Acl Andreas Enge
2014-11-08  7:39   ` Acl Mark H Weaver

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=87sihx1iyf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.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 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.