• Holding back pkgscr pkgs from pkgin?

    From met@met@ph.or to tilde.bsd on Thu Jul 13 03:33:37 2023
    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
  • From snowcrash@snowcrash@tilde.pink to tilde.bsd on Sat Sep 23 14:05:18 2023
    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