From: Marius Bakke <mbakke@fastmail.com>
To: guix-devel@gnu.org
Subject: Re: perl-digest-md5 , rev2
Date: Wed, 23 Nov 2016 19:30:16 +0100 [thread overview]
Message-ID: <87bmx6nj5z.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k2bunqb7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> I noticed the 'strip' phase was unable to strip MD5.so because of
> permissions, so I added a phase to chmod it 755.
I'm really sorry for the git noise regarding this package. Apparently
it's made read-only during the install phase, so the 'set-permissions'
phase has no effect.
I have a commit that fixes it, but upon further investigation this seems
to be the case for most/all perl packages. Only one other perl package
has a custom phase to fix it currently. Perhaps we should change
'perl-build-system' to make all .so files writable as well?
Alternatively, do it in 'gnu-build-system', as there are non-perl
packages with custom phases to make '.so' files writable as well.
Perhaps simply run a 'chmod 755' in the 'strip' phase? WDYT?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2016-11-23 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 13:52 [PATCH] Add perl-digest-md5 ng0
2016-11-22 13:52 ` [PATCH] gnu: " ng0
2016-11-22 19:55 ` [PATCH] " Marius Bakke
2016-11-22 23:57 ` perl-digest-md5 , rev2 ng0
2016-11-22 23:57 ` [PATCH] gnu: Add perl-digest-md5 ng0
2016-11-23 15:55 ` perl-digest-md5 , rev2 Marius Bakke
2016-11-23 16:06 ` ng0
2016-11-23 16:10 ` Marius Bakke
2016-11-23 18:30 ` Marius Bakke [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmx6nj5z.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).