Temat: Re: pkg upgrade with inverting match?
Data: 2026-03-19 17:41
Nadawca: "Miroslav Lachman" <[email protected]>
Adresat: "Paul Mather" <[email protected]>; 
DW: "Nikos Vassiliadis" <[email protected]>; "vermaden" 
<[email protected]>; "[email protected]" 
<[email protected]>; 

>> On 19/03/2026 14:42, Paul Mather wrote:
>> On Mar 19, 2026, at 7:29 am, Miroslav Lachman <[email protected]>
>> wrote:
> 
> [...]
> 
>>> First and most important (at least for me) would be a clear
>>> separation of base system upgrades from 3rd packages,
>>> without having to enter 40-character-long arguments.
>> 
>> 
>> The "pkg" command allows you to define aliases in pkg.conf.
>> So, if you wanted to save on typing, you could, say, define
>> "base-upgrade" and "ports-upgrade" aliases to restrict
>> "pkg upgrade" to just the appropriate repositories.
> 
> Yes, and everyone will fix it locally, each in their own way,
> so every computer will have a different command to achieve
> the same result. What an amazing time we live in.
> 
> I still don't think it's a good idea to combine base system
> updates and package upgrades into a single command by
> default. Now even something as simple as patch level
> security base update can completely break user's desktop
> if package upgrade runs at the same time and repository 
> happens to be missing such important packages as Firefox,
> Thunderbird, KDE / Plasma, etc.
> (missing packages that pkg upgrade then uninstalls from
> the local machine — I see this problem far too often)
> 
> Kind regards
> Miroslav Lachman



I was proposing the same idea since long time ago:

1.
Separate pkgbase(8) command that will only manipulate
FreeBSD 'Base System' and with SQLite database in the
/var/db/pkgbase/ directory.

2.
Separate pkg(8) command that will only manipulate
FreeBSD '3rd Party Software' and with SQLite database in
the /var/db/pkg/ directory.

... but seems that is just not wanted.



Regards,
vermaden


Reply via email to