![]() |
|
NetBSD Package System (pkgsrc) Installation and upgrading of packages on NetBSD. |
![]() |
|
Thread Tools | Display Modes |
|
||||
![]()
If I'm not mistaken, /etc/mk.conf is also used for building the kernel. Are you sure you want to build your kernel with all these fancy CPUFLAGS?
Whatever is only relevant for pkgsrc, I put in such a ifdef block Code:
.ifdef BSD_PKG_MK Fancy Stuff goes here .endif Glad to see another xv user ![]() |
|
||||
![]()
Hi [USER=2445]bashrules][/USER], thanks for replying
![]() Quote:
![]() Quote:
Quote:
![]()
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„ |
|
||||
![]()
Hello Sensucht,
I love pkgsrc for various reasons. One is the ability to nicely integrate custom patches via Code:
LOCALPATCHES= /home/bashrules/pkgsrc/patches Code:
$ cat ~/pkgsrc/patches/graphics/xv/patch-CREATOR.patch --- xvjpeg.c.orig 2012-02-14 22:52:40.000000000 -0800 +++ xvjpeg.c 2012-02-14 22:53:07.000000000 -0800 @@ -977,7 +977,6 @@ else comment = xvcmt; - jpeg_write_marker(&cinfo, JPEG_COM, (byte *)comment, (u_int)strlen(comment)); if (picExifInfo) jpeg_write_marker(&cinfo, JPEG_APP1, (byte *)picExifInfo, (u_int)picExifInfoSize); Pkgsrc is not perfect. There is always a package or two that does not build. If the problem is in the actual code, I can keep /usr/pkgsrc/ untouched and put my patch into LOCALPATCHES. Last edited by bashrules; 30th March 2020 at 03:09 AM. |
|
||||
![]() Quote:
- on one hand, one may dislike pkgsrc because a) each and every quarterly release breaks some package; b) deprecated software is systematically left there dying out, awaiting for somebody to take maintainership, if ever; c) support outside Tier I platforms is limited, while bootstrapping outside mainstream target (NetBSD, Illumos, macOS, Linux, QNX) is hackish at best and never devoid of unwanted surprises. Long gone are the days where pkgsrc would work almost shamelessly on IRIX, Solaris 10, HP-UX: I'd be surprised to hear about somebody having ccessfully built a pkgsrc-based HP-UX desktop on a PA-RISC workstation like here (2011) - on the other hand, I'm under the impression the majority of users can't help falling in love with it: it's simple, fast, powerful, portable, well-documented, hackable, and, most prominently, doesn't get in the way. For me its versatility is a killer feature: being able to use the same package manager on NetBSD and Slackware is something I'd hardly be able to live without now. Same goes for the cross toolchain (used it to build for evbarm64 on 8.99-current before binary packages became a reality). And the interesting thing is that I first moved to NetBSD after having used pkgsrc on Solaris/illumos first and macOS later. Promptly getting security patches on quarterly releases is another thing I endorse. Finally, it must be noted how easy is it to start contributing: the community is very inclusive and welcoming, eager to provide help and walk new committers through
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„ Last edited by Sehnsucht94; 31st March 2020 at 11:57 PM. Reason: further elaborated on a couple of points |
![]() |
Tags |
building, netbsd, options, package management, pkgsrc |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Seven Most .. please share with us .. | daemonfowl | Off-Topic | 19 | 29th July 2013 11:34 PM |
what are your best practices to ensure privacy ? | daemonfowl | OpenBSD Security | 11 | 4th April 2012 12:05 AM |
Disaster recovery best practices | RandomSF | FreeBSD General | 8 | 7th December 2010 06:41 AM |
Which is the significance about pkgsrc-2009Q2 and pkgsrc-2009Q3? | aleunix | NetBSD Package System (pkgsrc) | 3 | 16th December 2009 07:19 AM |
pf Share problem! | jleal | OpenBSD Security | 6 | 25th August 2008 04:08 AM |