From: Ulrich Mueller <ulm@gentoo.org> To: gentoo-dev@lists.gentoo.org Cc: "Michał Górny" <mgorny@gentoo.org>, gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] rfc: [patch] bash-completion-r1.eclass: add support for pkg-config for migration to the new upstream defined bash-completion directories (prereq for bug 472938) Date: Thu, 13 Jun 2013 08:59:45 +0200 [thread overview] Message-ID: <20921.28129.445590.862067@a1i15.kph.uni-mainz.de> (raw) In-Reply-To: <51B9657D.3000308@gentoo.org> >>>>> On Thu, 13 Jun 2013, Samuli Suominen wrote: > On 13/06/13 07:58, Michał Górny wrote: >> Dnia 2013-06-13, o godz. 01:22:11 Samuli Suominen >> <ssuominen@gentoo.org> napisał(a): >> >>> what $subject says, >>> >>> "add support for pkg-config for migration to the new upstream >>> defined bash-completion directories (prereq for bug 472938)" >>> >>> http://bugs.gentoo.org/472938 >>> >>> ie. the pkg-config file shipped *now* in portage is a hack from me >>> to postpone this >>> >>> pretty tired so more eyes is cool ;) >> >> You mean http://thread.gmane.org/gmane.linux.gentoo.devel/85258 ? >> >> I think you've got to convince ulm in the first place. > His concerns was actually already covered by the first post and the > linked bug: > This is required for smooth migration path from old to new > directories. Back when the old thread happened, there was only one > possible value for completions dir, now there is two. And nothing > prevents upstream adding/changing the values in the .pc file yet > again for next release, this should be dynamic -- just like > $(get_udevdir), $(get_libdir) etc. Nothing is covered. If you change the installation dir for the completion modules, then eselect bashcomp won't be able to find them any more. So you need a transition plan. Ulrich
WARNING: multiple messages have this Message-ID (diff)
From: Ulrich Mueller <ulm@gentoo.org> To: gentoo-dev@lists.gentoo.org Cc: "Michał Górny" <mgorny@gentoo.org>, gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: [patch] bash-completion-r1.eclass: add support for pkg-config for migration to the new upstream defined bash-completion directories (prereq for bug 472938) Date: Thu, 13 Jun 2013 08:59:45 +0200 [thread overview] Message-ID: <20921.28129.445590.862067@a1i15.kph.uni-mainz.de> (raw) Message-ID: <20130613065945.7yNnCbxGFjNS3NN_0as_Qisr044IRz3nClorJxmYnUs@z> (raw) In-Reply-To: <51B9657D.3000308@gentoo.org> >>>>> On Thu, 13 Jun 2013, Samuli Suominen wrote: > On 13/06/13 07:58, Michał Górny wrote: >> Dnia 2013-06-13, o godz. 01:22:11 Samuli Suominen >> <ssuominen@gentoo.org> napisał(a): >> >>> what $subject says, >>> >>> "add support for pkg-config for migration to the new upstream >>> defined bash-completion directories (prereq for bug 472938)" >>> >>> http://bugs.gentoo.org/472938 >>> >>> ie. the pkg-config file shipped *now* in portage is a hack from me >>> to postpone this >>> >>> pretty tired so more eyes is cool ;) >> >> You mean http://thread.gmane.org/gmane.linux.gentoo.devel/85258 ? >> >> I think you've got to convince ulm in the first place. > His concerns was actually already covered by the first post and the > linked bug: > This is required for smooth migration path from old to new > directories. Back when the old thread happened, there was only one > possible value for completions dir, now there is two. And nothing > prevents upstream adding/changing the values in the .pc file yet > again for next release, this should be dynamic -- just like > $(get_udevdir), $(get_libdir) etc. Nothing is covered. If you change the installation dir for the completion modules, then eselect bashcomp won't be able to find them any more. So you need a transition plan. Ulrich
next prev parent reply other threads:[~2013-06-13 7:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-12 22:22 [gentoo-dev] rfc: [patch] bash-completion-r1.eclass: add support for pkg-config for migration to the new upstream defined bash-completion directories (prereq for bug 472938) Samuli Suominen 2013-06-13 4:58 ` Michał Górny 2013-06-13 6:23 ` Samuli Suominen 2013-06-13 6:59 ` Ulrich Mueller [this message] 2013-06-13 6:59 ` Ulrich Mueller 2013-06-13 9:05 ` Samuli Suominen 2013-06-13 9:14 ` Ulrich Mueller 2013-06-13 9:30 ` Samuli Suominen 2013-06-13 15:25 ` Michał Górny 2013-06-13 16:29 ` Michał Górny
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=20921.28129.445590.862067@a1i15.kph.uni-mainz.de \ --to=ulm@gentoo.org \ --cc=gentoo-dev@gentoo.org \ --cc=gentoo-dev@lists.gentoo.org \ --cc=mgorny@gentoo.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox