FreeBSD Port: ports-mgmt/pkg

[Zsolt Ero]

Thanks for the 1.7.2 update, do you know when will it appear on quarterly?

On 5 April 2016 at 12:28, Zsolt Ero <zsolt.ero at gmail.com> wrote:
> I don't know how those tools internally check the state of packages,
> but anyone who self manages a server usually writes a long line of
> "pkg install -y pkg1 pkg2 pkg3" in a script. I would think that 99% of
> server deployment scripts are structured like this.
>
> Those lines are used in the sense of "make sure that pkg1, pkg2 and
> pkg3 are all installed after this command". Now the new change totally
> breaks this behaviour.
>
> Also, it breaks convention with known package managers from OS X or
> the linux world, where ... install is usually used as "make sure that
> ... is installed".
>
> Even if FreeBSD believes that such a huge change is somehow justified
> at a minor point release, it should be clearly communicated with the
> community. I would strongly recommend going back to the pre-1.7 way of
> "make sure that ... is installed" behaviour.
>
> Since this is such a fresh change, I believe there will be many more
> user reports coming in from broken install scripts soon.
>
> Zsolt
>
> On 5 April 2016 at 05:46, Brad Davis <brd at freebsd.org> wrote:
>> On Tue, Apr 05, 2016 at 02:20:49AM +0200, Zsolt Ero wrote:
>>> Hi,
>>>
>>> There is quite a serious regression in pkg 1.7.1: pkg install fails
>>> with error code 70 if any of the listed packages is already installed.
>>
>> Most tools like Puppet, Salt Stack, etc look at the output of `pkg list`.
>> What tool are you using?
>>
>> I don't think this is a regression at all.  pkg was not able to install
>> something, thus it should exit with a proper error code.
>>
>>
>> Regards,
>> Brad Davis
>>