From: Alex Vong <alexvong1995@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: util-linux and perl rename
Date: Mon, 26 Nov 2018 21:02:18 +0800 [thread overview]
Message-ID: <87bm6c2dr9.fsf@gmail.com> (raw)
In-Reply-To: <878t1gi59f.fsf@netris.org> (Mark H. Weaver's message of "Mon, 26 Nov 2018 03:58:41 -0500")
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> Alex Vong <alexvong1995@gmail.com> writes:
>
>> Thorsten Wilms <t_w_@freenet.de> writes:
>>
>>> I already had a "rename" binary via util-linux. Then I installed the
>>> package "rename", resulting in another "rename" binary, as I prefer
>>> the Perl version. This was a success in that I got what I wanted.
>>>
>>> However, should this name clash be considered a bug?
>>> Is there a policy for such circumstances?
>>> What happens that the newly installed "rename" gets precedence?
>>>
>> I think it is chosen based on some random criterions
>
> It's not random, but rather a very simple criterion. The packages
> listed first in the package manifest take priority over ones that come
> later. If you don't use manifests, "guix package -i <pkg>" puts <pkg>
> at the top of the new manifest, even if it was already present in the
> previous manifest.
>
I see, so this explains how Thorsten managed to get the right rename
(not because of luck or magic...)
I personally had given up using the imprerative "install" interface and
switched using the declarative "manifest" interface. IMO, it makes it
clearer what I've installed and allows me quickly comment / un-comment
fail-to-build packages. With the imprerative interface, I've to remember
which fail-to-build packages I didn't upgrade last time.
So in fact we have a 3rd solution: to re-order the packages in your
manifest.
> Mark
Cheers,
Alex
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2018-11-26 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 21:10 util-linux and perl rename Thorsten Wilms
2018-11-22 19:25 ` Danny Milosavljevic
2018-11-26 5:12 ` Alex Vong
2018-11-26 8:53 ` Thorsten Wilms
2018-11-26 8:58 ` Mark H Weaver
2018-11-26 13:02 ` Alex Vong [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=87bm6c2dr9.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).