pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

pkg/44526: Adding DragonFly support for bin-install target

>Number:         44526
>Category:       pkg
>Synopsis:       Adding DragonFly support for bin-install target
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 07 07:32:35 +0000 2011
>Originator:     Justin Sherrill
>Release:        DragonFly-2.8
DragonFly BSD
I've been building binary packages for DragonFly, and they get uploaded to  The 'pkg_radd' program on DragonFly sets 
BINPKG_SITES/PKG_PATH and runs pkg_add on its arguments, so that people can 
install binary packages (relatively) automagically.

I noticed that the bin-install target does close to the same thing, if you're 
on NetBSD.  The diffs here add the BINPKG_SITES setting appropriate for 

There's also a change for - `uname -r` on DragonFly can return 
x.y-RELEASE or x.y-DEVELOPMENT depending on version, and this adds '-' as an 
additional character for truncating the results from uname.

'bmake bin-install' on a DragonFly machine.

---     2011-02-06 21:52:45 -0500
+++  2011-02-06 21:53:19 -0500
@@ -640,7 +640,7 @@

-_SHORT_UNAME_R=        ${:!${UNAME} -r!:C@\.([0-9]*)[_.].*@.\1@} # 
n.n[_.]anything => n.n
+_SHORT_UNAME_R=        ${:!${UNAME} -r!:C@\.([0-9]*)[_.-].*@.\1@} # 
n.n[_.-]anything => n.n

 .include "install/"

--- 2011-02-06 21:39:11 -0500
+++      2011-02-06 21:41:07 -0500
@@ -32,6 +32,9 @@
 .if ${OPSYS} == "NetBSD"
 BINPKG_SITES?= \$${arch}/$${rel}
+.elif ${OPSYS} == "DragonFly"

Home | Main Index | Thread Index | Old Index