Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: Pacho Ramos <pacho@g.o>
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] News item review: bash-completion-2.1-r90
Date: Sun, 19 Oct 2014 10:47:44
Message-Id: 20141019124000.24bf94cd@pomiot.lan
In Reply to: Re: [gentoo-dev] News item review: bash-completion-2.1-r90 by Pacho Ramos
1 Dnia 2014-10-13, o godz. 12:23:52
2 Pacho Ramos <pacho@g.o> napisał(a):
3
4 > El lun, 13-10-2014 a las 11:35 +0200, Michał Górny escribió:
5 > > Please review the following news item.
6 > [...]
7 > > The current eselect-bashcomp setup will *not* be migrated. It may be
8 > > necessary to rebuild packages installing completions after the upgrade,
9 > > and remove old configuration symlinks afterwards. For details, please
10 > > consult the app-shells/bash-completion post-install messages.
11 > >
12 > >
13 >
14 > As I read in ebuild, the only additional information is about to run:
15 > $ find ${EPREFIX}/usr/share/bash-completion -maxdepth 1 -type f '!'
16 > -name 'bash_completion' -exec emerge -1v {} +
17 >
18 > For rebuilding packages installing in old location and to run:
19 > $ find ${EPREFIX}/etc/bash_completion.d -type l -delete
20 >
21 > for removing the old links
22 >
23 > Why not include this information in news item too? :)
24
25 Well, there were a few reasons:
26
27 1. I didn't want people to accidentally run the rebuild before updating
28 bash-completion.
29
30 2. ${EPREFIX} is substituted within ebuild.
31
32 3. Having a single doc source is easier to manage. Especially if I
33 improved the commands in the future.
34
35 But I guess having them here is fine too, esp. if you upgraded bashcomp
36 already.
37
38 --
39 Best regards,
40 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature