Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Feb 2009 11:16:44 -0900
From:      Mel <fbsd.questions@rachie.is-a-geek.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Force use of 'gpg2'
Message-ID:  <200902031116.44552.fbsd.questions@rachie.is-a-geek.net>
In-Reply-To: <20090203142833.65a72eae@scorpio>
References:  <20090203122406.1732b3f0@scorpio> <b79ecaef0902031103w43558a1ej5b2c22c7550f64d9@mail.gmail.com> <20090203142833.65a72eae@scorpio>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tuesday 03 February 2009 10:28:33 Jerry wrote:
> On Tue, 3 Feb 2009 19:03:01 +0000
> Chris Rees <utisoft@googlemail.com> wrote:
>
> [snip]
>
> >Try putting the link in somewhere that gets searched before
> >/usr/local/bin, like /bin or (better) /usr/bin. Then try rehash &&
> >which gpg
>
> I am using 'bash' so I don't think 'rehash' is going to do anything,
> although I could be mistaken. However, I don't see how that would stop
> a port from installing 'gpg' rather than 'gpg2'. I don't need both
> versions installed and would rather just keep the newer 'gpg2' one.

It would fit the RUN|BUILD_DEPENDS case, since gpg is looked for in $PATH. 
However, some ports check for gpgv and one even for ${PREFIX}/bin/gpgv, which 
would not help you.

You could run:
cd ${PORTSDIR:="/usr/ports"}
find . -depth 3 -name Makefile -exec fgrep -l security/gnupg1 {} + | xargs \
	your_filter_command_here

That filter command would have to rewrite the RUN|BUILD_DEPENDS line, so that 
it fits gnupg2.

Of course you can shorten the list and edit by hand if you only look at the 
ports that you actually use.

-- 
Mel

Problem with today's modular software: they start with the modules
    and never get to the software part.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?200902031116.44552.fbsd.questions>