I still use NetBSD on occasion and have been trying to make more
use of the pkgin[1] as this is now their prefered method for package management. Mostly the tool works however one issue I have is there
does not seem to be a way of marking a pkg as "held" the way the
Debian apt(8) system has apt-mark. In particular, I use the dwm window
manager which is customized via it's source code and compiled under /usr/pkgsrc/wm/dwm. I wish to have pkgin ignore the dwm pkg but nothing
I've tried has worked. The pkgin manpage seems to suggest using 'pkgin
import <file>' with a file containing a list of pkgs to update as a
possible method but even so pkgin overwrites my custom dwm binary..

If I can't find a pkgin-based solution I'll probably just install
dwm to /usr/local/bin completely outside of the pkgsrc system.

[1] https://pkgin.net/

--- Synchronet 3.19a-Linux NewsLink 1.113

On 13/07/23 at 03:33, met@ph.or <met@ph.or> wrote:

I still use NetBSD on occasion and have been trying to make more
use of the pkgin[1] as this is now their prefered method for package
management. Mostly the tool works however one issue I have is there
does not seem to be a way of marking a pkg as "held" the way the
Debian apt(8) system has apt-mark. In particular, I use the dwm window
manager which is customized via it's source code and compiled under
/usr/pkgsrc/wm/dwm. I wish to have pkgin ignore the dwm pkg but nothing
I've tried has worked. The pkgin manpage seems to suggest using 'pkgin
import <file>' with a file containing a list of pkgs to update as a
possible method but even so pkgin overwrites my custom dwm binary..

If I can't find a pkgin-based solution I'll probably just install
dwm to /usr/local/bin completely outside of the pkgsrc system.

[1] https://pkgin.net/

This is what I do on my systems; I keep a record of installed packages
using `pkg_chk -g' (generates a /usr/pkgsrc/pkgchk.conf), and manually
edit the file to remove the ones which have LOCALPATCHES [1].
Then I'll use `pkgin import /usr/pkgsrc/pkgchk.conf' to update
everything but the locallly maintained packages.


[1] https://www.unitedbsd.com/d/166-adding-patch-and-patch-file-to-a-pkgsrc-application/8
--- Synchronet 3.19b-Linux NewsLink 1.113

Re: Holding back pkgscr pkgs from pkgin?

From: snowcrash <snowcrash@tilde.pink>
Reply to: snowcrash
Date: Sat, 23 Sep 2023 14:05:18 -0000 (UTC)
Organization: tildeverse
Newsgroups:
tilde.bsd
Followup to: newsgroup
References:
<u8nrah$188vp$2@tilde.club>
On 13/07/23 at 03:33, met@ph.or <met@ph.or> wrote:

I still use NetBSD on occasion and have been trying to make more
use of the pkgin[1] as this is now their prefered method for package
management. Mostly the tool works however one issue I have is there
does not seem to be a way of marking a pkg as "held" the way the
Debian apt(8) system has apt-mark. In particular, I use the dwm window
manager which is customized via it's source code and compiled under
/usr/pkgsrc/wm/dwm. I wish to have pkgin ignore the dwm pkg but nothing
I've tried has worked. The pkgin manpage seems to suggest using 'pkgin
import <file>' with a file containing a list of pkgs to update as a
possible method but even so pkgin overwrites my custom dwm binary..

If I can't find a pkgin-based solution I'll probably just install
dwm to /usr/local/bin completely outside of the pkgsrc system.

[1] https://pkgin.net/

This is what I do on my systems; I keep a record of installed packages
using `pkg_chk -g' (generates a /usr/pkgsrc/pkgchk.conf), and manually
edit the file to remove the ones which have LOCALPATCHES [1].
Then I'll use `pkgin import /usr/pkgsrc/pkgchk.conf' to update
everything but the locallly maintained packages.

[1] https://www.unitedbsd.com/d/166-adding-patch-and-patch-file-to-a-pkgsrc-application/8

Long time since your post but anyway..

That's an interesting idea but I was a bit confused as the referenced link seems to outline a somewhat different scenario where local patches cause conflicts when updating the pkgsrc tree. My issue is more like the one
here [2], where pkgin binary pkg updates overwrite a pkgsrc-built pkg with
some localized tweaks.

I've since found that pkgin supports pkg-specific preferences, at least in terms of versioning, via /usr/pkg/etc/pkgin/preferred.conf [3]. That should
be sufficent for my needs; I can simply set "dwm=6.5" and if/when dwm-6.6
rolls around my local dwm-6.5 should remain untouched.

I did end up just building dwm as a non-pkgsrc pkg under /usr/local/ as it really is a simple WM with few dependancies but it's often much easier to locally patch something that's already in pkgsrc.

[2] https://www.unitedbsd.com/d/1447-pkgin-upgrade-question
[3] https://github.com/NetBSDfr/pkgin

--- Synchronet 3.20a-Linux NewsLink 1.2