Re: Questions about packages and ports
On Mon, 2005-06-27 at 13:25 -0500, Nikolas Britton wrote:
On a similar note can someone remind me how to set the remote package
site for pkg_add and portupgrade -P? I remember it had something to do
with setenv but don't remember the variable it uses and I've never
used the portupgrade -P option before.
It requires a bit of rtfm it seems...
$ man -P /bin/cat pkg_add | grep --context=2 -- -r
what you are doing!
-r Use the remote fetching feature. This will determine the appro-
priate objformat and release and then fetch and install the pack-
age.
--
The environment variable PACKAGEROOT specifies an alternate location for
pkg_add to fetch from. The fetch URL is built using this environment
variable and the automatic directory logic that pkg_add uses when the -r
option is invoked. An example setting would be ftp://ftp3.FreeBSD.org;.
The environment variable PACKAGESITE specifies an alternate location for
pkg_add to fetch from. This variable subverts the automatic directory
logic that pkg_add uses when the -r option is invoked. Thus it should be
a complete URL to the remote package file(s).
$
( - By the way, if anyone knows a simpler way of achieving that man/grep
combination, please tell!)
I couldn't find any documented reference as to where to put the env
setting, so I presume I must have either stumbled upon it while browsing
pkgtools.conf or seen it in an answer here or on a web page somewhere...
$ grep --context=2 PACKAGEROOT /usr/local/etc/pkgtools.conf
#Equivalent to:
# sprintf('%s/pub/FreeBSD/ports/%s/packages-%s/',
# root || ENV['PACKAGEROOT'] || 'ftp://ftp.FreeBSD.org',
# OS_PLATFORM, OS_PKGBRANCH)
#
--
# ENV['PKG_FETCH'] = curl '%s' -o '%s'
# ENV['PKG_FETCH'] = 'false'# never fetch packages from a remote
site
# ENV['PACKAGEROOT'] = 'ftp://ftpN.XX.FreeBSD.org'
ENV['PORTSDIR'] ||= '/usr/ports'
ENV['PACKAGES'] ||= ENV['PORTSDIR'] + '/packages'
ENV['PKG_PATH'] ||= ENV['PACKAGES'] + '/All'
# 20040210 ws - added PACKAGEROOT
ENV['PACKAGEROOT'] = 'ftp://ftp.au.FreeBSD.org'
# SANITY_CHECK: boolean (default: true)
$
You probably worked it out already but I thought this one was worthwhile
to toss in to the archives, and perhaps prompt someone to contemplate a
revision for the handbook.
hth
Wayne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions about packages and ports
I like to use the pkg_add -r feature of FreeBSD, however I have run into a problem where the ports have a more current version of the app then the package of the same app. It seems the ports collection is updated more then the package collection is this true? Is the maintainer of a package and a port the same person? Are they responsible for updating the package and the port? Packages will download dependencys required by the app does the ports do this as well? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about packages and ports
Sean Murphy wrote: I like to use the pkg_add -r feature of FreeBSD, however I have run into a problem where the ports have a more current version of the app then the package of the same app. It seems the ports collection is updated more then the package collection is this true? Yes. Packages are built from ports, so you can expect the ports collection version to be as current or more current than the available packages. Is the maintainer of a package and a port the same person? Are they responsible for updating the package and the port? I don't believe so, or at least it's not a requirement that I know of. All maintainers are volunteers, and the load of maintaining the port and building and distributing packages is typically distributed over many volunteers. Packages will download dependencys required by the app does the ports do this as well? I think this depends on the options that you specify (for either packages or ports). Typically, though -- yes, building a port will automatically build the dependencies. More about packages ports can be found in Chap. 4 of the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about packages and ports
On 6/27/05, Sean Murphy [EMAIL PROTECTED] wrote: I like to use the pkg_add -r feature of FreeBSD, however I have run into a problem where the ports have a more current version of the app then the package of the same app. It seems the ports collection is updated more then the package collection is this true? Yes Is the maintainer of a package and a port the same person? Are they responsible for updating the package and the port? Yes and No Packages will download dependencys required by the app does the ports do this as well? Yes --- On a similar note can someone remind me how to set the remote package site for pkg_add and portupgrade -P? I remember it had something to do with setenv but don't remember the variable it uses and I've never used the portupgrade -P option before. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about packages and ports
* Sean Murphy [2005-06-27 10:59 -0700] I like to use the pkg_add -r feature of FreeBSD, however I have run into a problem where the ports have a more current version of the app then the package of the same app. It seems the ports collection is updated more then the package collection is this true? The packages are automatically built from the port-collection. So a package is a binary pre-build version of the corresponding port. The ports collection are updated several times a day, while the rebuild-process takes a long time. This compilation takes place on the package building clusters (pointyhat.freebsd.org and some other cluster of which I cannot remember the name). Once the peckages have been built, they're uploaded to the master ftp-site, and will then be propagated to the mirror-sites. The packages are rebuilt about once a week, I think. Is the maintainer of a package and a port the same person? Are they responsible for updating the package and the port? Since the packages are automatically built, they don't have a maintainer in the same way as the ports do. I guess it is the Release Engineer team that's in charge of the packages that come with a release, but the one's that's on the ftp-sites are just automatically built from the ports. This process is prone to errors, and if a port becomes broken, I guess the corresponding package might get out-of-date. You could take a look at the errorlog on pointyhat.freebsd.org, but I'm not too sure about this process. Someone else could probably fill in the blanks. Or you could do a search on the web. I'm sure this process is described in detail somwhere. Bottom line is that the port maintainer makes sure that the port is buildable. The pointyhat-cluster then builds it to make a package. The package as such, has no maintainer of its own. Packages will download dependencys required by the app does the ports do this as well? Yes! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
