Bug 151187

Summary: pkg(8): allow different pkgdep location
Product: Base System Reporter: grarpamp
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed Overcome By Events    
Severity: Affects Some People    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description grarpamp 2010-10-04 00:10:04 UTC
pkg_add(1) needs to be able to fetch the primary package file
[pkg-name argument] from one location and any dependencies
[+CONTENTS: @pkgdep] from a second location.

In other words, these two examples should be made to work.

# remote pkg-name
PKGDEPSITE=ftp://ftp.freebsd.org/.../All/ \
 pkg_add ftp://ftp.example.com/.../foo.tgz

# local pkg-name
PKGDEPSITE=ftp://ftp.example.com/.../pkg/ \
 pkg_add /home/.../foo.tgz


Also, consider enhancing the 'path' type environment
variables to allow multiple paths/methods in order:

PKG_PATH=/foo:'ftp://1.com/':'http://2.com/':'ftp://ftp.freebsd.org/'
Comment 1 grarpamp 2010-10-04 03:14:32 UTC
One of the reasons this is needed is to allow
develop[ment/ers] of local code or packages to
easily bring in libraries and things they need.
Without having to build and deal with them
locally. Automation of build environments.

Less or selected bandwidth use.

Another case is openoffice. 2.4.x is outdated
and good-day does not carry the deps for any
version, thus it needs manual intervention and
pointing to freebsd.org/mirror to install the deps.
Comment 2 Baptiste Daroussin freebsd_committer freebsd_triage 2014-08-26 05:56:09 UTC
pkg_* tools are discontinued
Comment 3 grarpamp 2014-09-04 19:06:06 UTC
Reopened... concepts still apply to pkg(8).
Comment 4 grarpamp 2014-09-04 19:07:06 UTC
Reopened... concepts still apply to pkg(8).
Comment 5 Baptiste Daroussin freebsd_committer freebsd_triage 2015-05-29 10:37:23 UTC
The concept does not really apply to pkg(8) as pkg supports multiple repositories