Hi,
On Wednesday, June 28, 2017 10:42 CEST, Raf Czlonka <rczlonka@gmail.com> wrote:
> On Wed, Jun 28, 2017 at 07:50:38AM BST, Sebastian Reitenbach wrote:
> > Hi,
>
> Hi Sebastian,
>
> > attached patch updates puppet to 4.10.4 as well as changing the
> > way packages are installed. Up to now it was looking into a
> > /etc/pkg.conf, but since that is not there anymore, you may run
> > into problems, if you don't have PKG_PATH exported. Now /etc/pkg.conf
> > is not consulted anymore, pkg_add is just doing it's magic, you
> > still can export PKG_PATH.
>
> After pkg_add(1) manual page:
>
> If the given package names are not
> found in the current working directory, pkg_add will search for them in
> each directory (local or remote) named by the TRUSTED_PKG_PATH
> environment variable, then the PKG_PATH environment variable. The
> special url 'installpath' refers to the contents of installurl(5). If
> neither TRUSTED_PKG_PATH nor PKG_PATH are defined, pkg_add will use
> './:installpath' as a default.
>
> > If I don't hear anything I'll go ahead with it on the weekend.
>
> Shouldn't it then fall back to using /etc/installurl if neither
> of the above are defined - akin to the way it used to work with
> /etc/pkg.conf?
given that I understand the pkg_add(1) manual page correctly,
pkg_add is automatically falling back to whatever is defined in
installurl(5) therefore I think, teaching puppet how to parse that file
and make sense of it would be superfluous?
cheers,
Sebastian
>
> Regards,
>
> Raf
No comments:
Post a Comment