Re: Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
Hugh bo...@gmail.com wrote: A question i've got is where i can find the default PACKAGESITE value? It seems to be hardcoded in usr.sbin/pkg_install/add/main.c (line 318 in the 8.1 version). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
A question i've got is where i can find the default PACKAGESITE value? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
2011/12/4, Hugh bo...@gmail.com: A question i've got is where i can find the default PACKAGESITE value? FreeBSD comes with the default mirror (ftp), see when you use pkg_add, in my case it failed, is the reason because i changed to the mirror (ftp), you can use diferent ftp ftp://ftp.freebsd.org/pub/FreeBSD/ -- Edguitar ;) http://cybernautape.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
Hi guys, currently i have a machine with freebsd 9 rc2, for default when i try to use pkg_add -r wget, for example, i can not install because the path is freebsd# pkg_add -r xscreensaver Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz' by URL but i put : freebsd# setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/ freebsd# pkg_add -r xscreensaver Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/xscreensaver.tbz... Done. it works, pero i want to use for default, without put again it, when the machine reboot and i want to use again pkg i am puting the path manually :(, what is the file when i should put the path? to use pkg_add -r package?, without put again PACKAGESITE?, thank in advance! http://cybernautape.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
you may want to define the PACKAGESITE variable in the .cshrc file in your $HOME; On Wed, Nov 30, 2011 at 1:27 PM, Edgar Rodolfo cybernaut...@gmail.comwrote: Hi guys, currently i have a machine with freebsd 9 rc2, for default when i try to use pkg_add -r wget, for example, i can not install because the path is freebsd# pkg_add -r xscreensaver Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz : File unavailable (e.g., file not found, no access) pkg_add: unable to fetch ' ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz ' by URL but i put : freebsd# setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/ freebsd# pkg_add -r xscreensaver Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/xscreensaver.tbz. .. Done. it works, pero i want to use for default, without put again it, when the machine reboot and i want to use again pkg i am puting the path manually :(, what is the file when i should put the path? to use pkg_add -r package?, without put again PACKAGESITE?, thank in advance! http://cybernautape.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setenv PACKAGESITE thepathtoftp, in boot time how to do it?
2011/11/30, Alexander Kapshuk alexander.kaps...@gmail.com: you may want to define the PACKAGESITE variable in the .cshrc file in your $HOME; Thank. this is correct: echo 'setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/Latest/;' /root/.cshrc On Wed, Nov 30, 2011 at 1:27 PM, Edgar Rodolfo cybernaut...@gmail.comwrote: Hi guys, currently i have a machine with freebsd 9 rc2, for default when i try to use pkg_add -r wget, for example, i can not install because the path is freebsd# pkg_add -r xscreensaver Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz : File unavailable (e.g., file not found, no access) pkg_add: unable to fetch ' ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/xscreensaver.tbz ' by URL but i put : freebsd# setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/ freebsd# pkg_add -r xscreensaver Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/xscreensaver.tbz. .. Done. it works, pero i want to use for default, without put again it, when the machine reboot and i want to use again pkg i am puting the path manually :(, what is the file when i should put the path? to use pkg_add -r package?, without put again PACKAGESITE?, thank in advance! http://cybernautape.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Edguitar ;) http://cybernautape.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
rookie question about PACKAGESITE
Hello all, I started using FreeBSD about a week ago, and I really like the system. Have been using Linux for the last few years. One noob question though, according to the Handbook on Packages and Ports, I can use packages for either RELEASE, STABLE, or CURRENT. How exactly would this compare to Linux? Is it that CURRENT is like Fedora(bleeding-edge and somewhat unstable), and STABLE is like RedHat Enterprise Linux (older versions of software, but very stable)? Which one should I use? I am currently using RELEASE. I am not looking for bleeding edge. I'm after stability. Kind regards, Coert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rookie question about PACKAGESITE
Hey hey Coert Nice to see another GLUG member on here. The link below will answer you're question. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html In general give the FreeBSD Handbook a read, in my concerted little opinion it is the gold standard in how any operating system should be documented. On Tue, May 11, 2010 at 1:42 PM, Coert lgro...@waagmeester.co.za wrote: Hello all, I started using FreeBSD about a week ago, and I really like the system. Have been using Linux for the last few years. One noob question though, according to the Handbook on Packages and Ports, I can use packages for either RELEASE, STABLE, or CURRENT. How exactly would this compare to Linux? Is it that CURRENT is like Fedora(bleeding-edge and somewhat unstable), and STABLE is like RedHat Enterprise Linux (older versions of software, but very stable)? Which one should I use? I am currently using RELEASE. I am not looking for bleeding edge. I'm after stability. Kind regards, Coert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rookie question about PACKAGESITE
On Tue, 11 May 2010 13:42:52 +0200 Coert lgro...@waagmeester.co.za wrote: Hello all, I started using FreeBSD about a week ago, and I really like the system. Have been using Linux for the last few years. One noob question though, according to the Handbook on Packages and Ports, I can use packages for either RELEASE, STABLE, or CURRENT. Current is bleeding edge, STABLE branches are stable development branches, but these all relate to the base system. As far as packages are concerned, they should be be built for the base system version you are using - you can mostly get away with using STABLE packages on releases, but it can cause problems. If you want to keep to keep packages up-to-date between releases, update via ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PACKAGESITE Directory Structure
On Thursday 18 June 2009 18:31:02 Glen Barber wrote:
Hello, list.
After trying to figure out the incorrect directory structure for some
of the packages hosted on my site, I am at a loss.
After reading through /usr/src/usr.sbin/pkg_install/add/main.c from
HEAD, lines 337-340 seems to suggest that if 'Latest' is not found,
'All' is implied to pkg_add when PACKAGESITE is explicitly defined
(otherwise overridden with hard-coded values).
The most intuitive PACKAGESITE is the one pointing to the directory *before*
All including trailing slash. This way one can add packages by origin, which
is more human friendly then knowing the specific version or what the mangled
LATEST_LINK is. pkg_add will then do the right thing with respect to
dependencies.
But to explain the PACKAGESITE variable: it is expected to point to the final
location (including trailing slash) for the command line argument(s) given.
pkg_add will try to figure out how to get to 'All/' and 'Latest/' the best it
can if the url ${PACKAGESITE}$1 returns not found and for dependencies.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PACKAGESITE Directory Structure
Hello, list. After trying to figure out the incorrect directory structure for some of the packages hosted on my site, I am at a loss. After reading through /usr/src/usr.sbin/pkg_install/add/main.c from HEAD, lines 337-340 seems to suggest that if 'Latest' is not found, 'All' is implied to pkg_add when PACKAGESITE is explicitly defined (otherwise overridden with hard-coded values). With that, I am still trying to figure out the proper hierarchy: Scenario 1.) If I 'pkg_add -r foo.3.2_1.tbz' from www.example.com/packages, should 'All' be implied after 'packages' (packages/All)? Scenario 2.) Same pkg_add command from www.example.com/packages/mybinary/package -- should 'All' be a subdirectory of packages/ or mybinary/? It appears that this if 'Latest/' is not found, overwrite as 'All/' may be expected, but I am getting conflicting output. Any input is appreciated. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [pkg_add] PACKAGESITE weirdness - URL not correct for dependencies?
On Thursday 26 March 2009 21:46:07 L Campbell wrote: Okay, so apparently there's some serious weirdness in the logic in src/usr.sbin/pkg_install/lib/url.c, in fileGetURL. This function takes two parameters, base and spec, and has the following behavior -- snip behavior and patch Yes, it is a bit counter-intuitive. However it's documented in the pkg_add(1) manpage that PACKAGESITE should resolve to the full URL where packages can be found (even the trailing slash). I've found in practice, that it is the easiest to set your webroot below All/, so that All/foo-1.2.3.tbz resolves to the foo 1.2.3 package. Then also maintain the various categories links like devel/foo.tbz and as human use pkg_add like so: pkg_add -r devel/foo This will do the right thing(tm) and you don't have to look up/remember the version numbers as a bonus. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [pkg_add] PACKAGESITE weirdness - URL not correct for dependencies?
On Sat, Mar 28, 2009 at 7:37 AM, Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Thursday 26 March 2009 21:46:07 L Campbell wrote: Okay, so apparently there's some serious weirdness in the logic in src/usr.sbin/pkg_install/lib/url.c, in fileGetURL. This function takes two parameters, base and spec, and has the following behavior -- snip behavior and patch Yes, it is a bit counter-intuitive. However it's documented in the pkg_add(1) manpage that PACKAGESITE should resolve to the full URL where packages can be found (even the trailing slash). The additional stipulation that any dependent packages must be in an ../All/ directory relative to the path of the initial package is an undocumented feature. It's a bit counter-intuitive, but once it works, it works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[pkg_add] PACKAGESITE weirdness - URL not correct for dependencies?
I'm running a bunch of jails and running the same set of ports between them. To save myself some CPU time, I've got one jail building packages for everything I need, then serving those packages out over HTTP to the rest of the jails. The package serving jail is at 10.0.0.4, and is serving packages out from it's HTTP root, such that requesting the following URLs properly fetch the desired packages: http://10.0.0.4/lighttpd-1.4.22.tbz http://10.0.0.4/pcre-7.8.tbz I set PACKAGESITE to 'http://10.0.0.4/'; when I attempt to install Lighttpd with pkg_add -rv, I get the following output (snipped to relevant portions): $ pkg_add -rv lighttpd-1.4.22 (..snip..) scheme: [http] user: [] password: [] host: [10.0.0.4] port: [0] document: [/lighttpd-1.4.22.tbz] (..fetches and installs lighttpd-1.4.22 properly..) Package 'lighttpd-1.4.22' depends on 'pcre-7.8' with 'devel/pcre' origin. scheme: [http] user: [] password: [] host: [All] port: [0] document: [/pcre-7.8.tbz] --- All:80 looking up All Error: FTP Unable to get http://All/pcre-7.8.tbz: No address record Somewhere along the process, something breaks and 'host' doesn't get set properly. I'm currently poking through the pkg_install code to figure out wtf is going on, but I figured I'd prod the lists to see if anyone else hit a similar problem (or knows what I'm doing wrong) since I'm not familiar with it. $ uname -a FreeBSD blah 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks :3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [pkg_add] PACKAGESITE weirdness - URL not correct for dependencies?
On Thu, Mar 26, 2009 at 3:37 PM, L Campbell ll...@virginia.edu wrote: blah Oh, and please CC me on any replies since I don't follow this list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [pkg_add] PACKAGESITE weirdness - URL not correct for dependencies?
Okay, so apparently there's some serious weirdness in the logic in
src/usr.sbin/pkg_install/lib/url.c, in fileGetURL. This function takes
two parameters, base and spec, and has the following behavior --
* if spec is a valid URL, it's used unchanged as the path to the remote package.
* if base is non-NULL, the last two '/'s are chopped off and All/ +
package name + .tbz is used as the result.
* if PKG_ADD_BASE is set in the environment, it's concatenated with
the package name and .tbz
When fileGetURL is called on the dependencies by pkg_do in
add/perform.c, it always gets passed the remote URL of the parent
package as the base and the package name as the spec, so the second
branch is always taken.
Unfortunately, this doesn't work with the PACKAGESITE code in
add/main.c, because fileGetURL is expecting the base argument to be of
the form http://host/directory/package.tbz;, as in
www/lighttpd-1.4.22.tbz. The problem is, when using PACKAGESITE, the
actual URL (in my case) is just http://host/lighttpd-1.4.22.tbz;, so
that gets incorrectly chopped down to http:/ + Add/ +
lighttpd-1.4.22.tbz.
It works fine if your PACKAGESITE puts all the packages in the All/
subdirectory (as I think the official ones do), but at the very least,
that's an undocumented constraint.
My solution was to add another case into fileGetURL which gets
overrides the three currently in there and is invoked if and only if
PACKAGESITE is set in the environment.
The following patch makes it work for me --
--- usr.sbin/pkg_install/lib/url.c.orig 2009-03-26 19:56:12.0 +
+++ usr.sbin/pkg_install/lib/url.c 2009-03-26 20:41:44.0 +
@@ -57,7 +57,21 @@
* to construct a composite one out of that and the basename we were
* handed as a dependency.
*/
- if (base) {
+ if (getenv(PACKAGESITE)) {
+ if (strlcpy(fname, getenv(PACKAGESITE), sizeof(fname))
+ = sizeof(fname)) {
+ return NULL;
+ }
+ if (strlcat(fname, spec, sizeof(fname))
+ = sizeof(fname)) {
+ return NULL;
+ }
+ if (strlcat(fname, .tbz, sizeof(fname))
+ = sizeof(fname)) {
+ return NULL;
+ }
+ }
+ else if (base) {
strcpy(fname, base);
/*
* Advance back two slashes to get to the root of the package
Though I think, in the long-run I'm just going to put all my packages
in http://10.0.0.4/All/ and call it a day -- I hate maintaining a
bunch of patches for stuff.
:(
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PACKAGESITE
At 2008-07-12T21:59:09-07:00, [EMAIL PROTECTED] wrote: Can someone provide a correct example of setting PACKAGESITE so that pkg_add will find the 7-stable packages for i386? I have tried ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ You could use the `-r' option of pkg_add(1) to enable remote fetching. % setenv PACKAGESITE 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/' % pkg_add -rv expat scheme: [ftp] user: [] password: [] host: [ftp.freebsd.org] port: [0] document: [/pub/FreeBSD/ports/i386/packages-7-stable/Latest/expat.tbz] --- ftp.freebsd.org:21 looking up ftp.freebsd.org connecting to ftp.freebsd.org:21 220 Welcome to freebsd.isc.org. USER anonymous 331 Please specify the password. PASS [EMAIL PROTECTED] 230 Login successful. PWD 257 / CWD pub/FreeBSD/ports/i386/packages-7-stable/Latest 250 Directory successfully changed. MODE S 200 Mode set to S. TYPE I 200 Switching to Binary mode. setting passive mode PASV 227 Entering Passive Mode (204,152,184,73,88,54) opening data connection initiating transfer RETR expat.tbz 150 Opening BINARY mode data connection for expat.tbz (148302 bytes). Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/expat.tbz... Raghavendra. -- N. Raghavendra [EMAIL PROTECTED] | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Can someone provide a correct example of setting PACKAGESITE so that pkg_add will find the 7-stable packages for i386? I have tried ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ as shown in the handbook, and also: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable and all have failed. I get messages like pkg_add: could not find package expat-2.0.1 ! pkg_add: could not find package png-1.2.28 ! pkg_add: could not find package pkg-config-0.23_1 ! etc. Even specifying -v does not cause pkg_add to show exactly [...] Did you specify the -r flag? Without that, the PACKAGESITE environment variable is note used. From the ENVIRONMENT section of pkg_add(1): 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). -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
At 2008-07-12T21:59:09-07:00, [EMAIL PROTECTED] wrote: Can someone provide a correct example of setting PACKAGESITE so that pkg_add will find the 7-stable packages for i386? I have tried ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ If you are running 7-STABLE, setting `PACKAGESITE' to the above value is unnecessary [Handbook, 4.4.1, Note]: pkg_add(1) will download the latest version of your application if you are using FreeBSD-CURRENT or FreeBSD-STABLE. In that case, just the `-r' option to pkg_add(1) will do. % uname -r 7.0-STABLE % unsetenv PACKAGESITE % echo $PACKAGESITE PACKAGESITE: Undefined variable. % pkg_add -rv expat scheme: [ftp] user: [] password: [] host: [ftp.freebsd.org] port: [0] document: [/pub/FreeBSD/ports/i386/packages-7-stable/Latest/expat.tbz] --- ftp.freebsd.org:21 looking up ftp.freebsd.org connecting to ftp.freebsd.org:21 220 Welcome to freebsd.isc.org. USER anonymous 331 Please specify the password. PASS [EMAIL PROTECTED] 230 Login successful. PWD 257 / CWD pub/FreeBSD/ports/i386/packages-7-stable/Latest 250 Directory successfully changed. MODE S 200 Mode set to S. TYPE I 200 Switching to Binary mode. setting passive mode PASV 227 Entering Passive Mode (204,152,184,73,68,212) opening data connection initiating transfer RETR expat.tbz 150 Opening BINARY mode data connection for expat.tbz (148302 bytes). Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/expat.tbz... Raghavendra. -- N. Raghavendra [EMAIL PROTECTED] | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
Did you specify the -r flag? Without that, the PACKAGESITE environment variable is note used ... No, I didn't, because -- unless I am misunderstanding the description of the -r flag -- that will cause pkg_add to look *only* on the FTP site. I want it to use packages that have already been downloaded, and use the FTP site only when a needed package is not available locally. I'm trying to install an already-downloaded 10MB package which has quite a few dependencies, several of which were already fetched during a previous attempt. IOW I want the equivalent of specifying the current directory, followed by the FTP site, in PKG_PATH; but the colon in the URL messes that up by looking like a pathname separator. If I tried something like setenv PKG_PATH .:ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/ it would look first in the current directory, then in a subdirectory named ftp, and finally in a directory named //ftp.freebsd.org/... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
[EMAIL PROTECTED] wrote: Did you specify the -r flag? Without that, the PACKAGESITE environment variable is note used ... No, I didn't, because -- unless I am misunderstanding the description of the -r flag -- that will cause pkg_add to look *only* on the FTP site. I want it to use packages that have already been downloaded, and use the FTP site only when a needed package is not available locally. I'm trying to install an already-downloaded 10MB package which has quite a few dependencies, several of which were already fetched during a previous attempt. IOW I want the equivalent of specifying the current directory, followed by the FTP site, in PKG_PATH; but the colon in the URL messes that up by looking like a pathname separator. If I tried something like setenv PKG_PATH .:ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/ it would look first in the current directory, then in a subdirectory named ftp, and finally in a directory named //ftp.freebsd.org/... ___ PKG_PATH is for directories only, it will not do FTP. from man pkg_add: The value of the PKG_PATH is used if a given package cannot be found. The environment variable should be a series of entries separated by colons. Each entry consists of a directory name. If I understand well, what you are asking is for pkg_add to: - Search all local paths (in PKG_PATH) for a dependency - If not found, use PACKAGESITE to download from a site. As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way, but I might be wrong. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
On Sunday 13 July 2008, Manolis Kiagias wrote: As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way, but I might be wrong. I wonder if portinstall -P (or even -PP) might do what the OP wants? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
At 2008-07-13T01:33:18-07:00, [EMAIL PROTECTED] wrote: IOW I want the equivalent of specifying the current directory, followed by the FTP site, in PKG_PATH; AFAIK, in FreeBSD, the entries in PKG_PATH must be directories, not URLs. (NetBSD and OpenBSD seem to allow URLs in that variable: http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add ) Raghavendra. -- N. Raghavendra [EMAIL PROTECTED] | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
Mike Clarke wrote: On Sunday 13 July 2008, Manolis Kiagias wrote: As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way, but I might be wrong. I wonder if portinstall -P (or even -PP) might do what the OP wants? I am using portupgrade for upgrading from source myself, but have never used portinstall with packages. You are correct, according to the man page, portinstall -PP would be his best bet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way ... I wonder if portinstall -P (or even -PP) might do what the OP wants? You are correct, according to the man page, portinstall -PP would be his best bet. Except that portinstall is part of portupgrade, which has its own boatload of dependencies. Is there any way to do this with, say, portmaster? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
[EMAIL PROTECTED] wrote: As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way ... I wonder if portinstall -P (or even -PP) might do what the OP wants? You are correct, according to the man page, portinstall -PP would be his best bet. Except that portinstall is part of portupgrade, which has its own boatload of dependencies. You must be used to sailing in very small boats. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
[EMAIL PROTECTED] wrote: As far as I know, pkg_add will only fetch dependencies recursively from the Internet when used with -r but it will then ignore PKG_PATH. Seems what you are asking cannot be done this way ... I wonder if portinstall -P (or even -PP) might do what the OP wants? You are correct, according to the man page, portinstall -PP would be his best bet. Except that portinstall is part of portupgrade, which has its own boatload of dependencies. Is there any way to do this with, say, portmaster? Not yet. :) Doug -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PACKAGESITE
... portinstall is part of portupgrade, which has its own boatload of dependencies. You must be used to sailing in very small boats. From lurking on questions@ for a while, I have gotten the impression that ruby alone would pretty well fill up a Panamax :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PACKAGESITE
Can someone provide a correct example of setting PACKAGESITE so that pkg_add will find the 7-stable packages for i386? I have tried ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ as shown in the handbook, and also: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable and all have failed. I get messages like pkg_add: could not find package expat-2.0.1 ! pkg_add: could not find package png-1.2.28 ! pkg_add: could not find package pkg-config-0.23_1 ! etc. Even specifying -v does not cause pkg_add to show exactly where it is looking (which might provide a clue as to what the correct setting would look like). The pkg_add manpage shows an example for PACKAGEROOT, but not for PACKAGESITE. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
First off, thanks to Kris and Mel for the previous definitive answers. Let me see if I can summarize this correctly... 1) It's important that administrators who are taking advantage of pre-compiled packages (like me) use packages that have been compiled for their particular base system. 2) For users running a release base system, there is set of pre-compiled packages provided for use with their particular release. These are the packages found on the FTP site in the release folders on the FTP site. 3) The default behavior for pkg_add -r on RELEASE systems is to source it's pre-compiled packages from the release directory matching the underlying base-system's release. For a 6.2-RELEASE base system (for i386), pkg_add -r will source packages from... /pub/FreeBSD/ports/i386/packages-6.2-release 4) Those release packages are never updated for any reason. The list of available packages neither increases nor decreases, the versions of the packages made available doesn't change, and (presumably) the packages are never recompiled once the release has occurred. It's a static list of packages compiled (and tested) for a particular release and then never touched again. 5) If an admin wants to install pre-compiled packages that are not present in the default release directory, they can configure pkg_add -r to source packages from one of the other package directories by setting the PACKAGESITE environment variable to point to one of the other package directories. 6) Care should be taken when re-pointing PACKAGESITE as it would then be possible for you to install a package that's been compiled against a different version of some base-system library than you are currently running. How'd I do? Assuming I did well, a couple of more questions... 1) Regardless of what base-system version you install, eventually the base system will need to be updated (in the least, to apply security updates). So generally one important decision is what version of FreeBSD you're going to track when doing updates. Security? Stable? Current? So what's the recommended application install-procedure if you start with a release system and then track security via freebsd-update? (A common scenario, I presume.) It would seem that pkg-add -r is a no-go in this case. If you leave pkg_add -r pointing to it's default source, it'll grab packages compiled against the release system which, while unlikely, may have libraries incompatible with your new base system that's tracking security. If you change pkg-add -r to source from stable or release you're getting packages compiled against a base-system even more different than your own security base system. As far as I can tell there is not set of pre-compiled packages that have been compiled against the secure track. 2) How does pkg_add -r know it's on a release system? The handbook says that pkg_add -r will download from either the current, stable, or release package directories as appropriate. How does it know I have a release system and not a stable system? Particularly since my system is not *really* a release system once I do my first freebsd-update, right?. At that point it becomes a system tracking secure, right? Thanks again for the input so far. The package thing is making way more sense, hopefully a few more clarifications and I'll grok it. Thanks, - Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
Gary Affonso wrote: If I do, it seems to me that the absolute first thing I should do after installing a release version would be to change where pkg_add -r is sourcing packages from. Either to current if I like to live on the edge or stable if I want to be a more conservative. No, stable and current here refer to the branches of FreeBSD that the packages are compiled to run with, there are no other differences in the contents of the packages themselves. I'm curious, why does pkg_add -r point to the release snapshot of ports by default? Is the idea that a release is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with pkg_add -r? Seems to me it would be better to have pkg_add -r point to stable (which, if I understand things correctly, does get updated packages). -release packages have gone through an extensive period of testing with that release, so you have more confidence they will work. The up-to-date packages may not work, may not even be present on the FTP site, and in general are not suitable for users who just want a working system without having to fiddle with it. i.e. defaulting to the packages that came with the release is a conservative step that is appropriate for users who just want packages that work, and don't care about always having the latest versions. For the rest of you, you're going to be doing a lot more hands on admin anyway, so setting one env variable is not a heavy burden. And how does one go about *permanently* changing the pkg_add -r target. You can set the PACKAGESITE variable in the shell which will work on a user-by-user basis but isn't there a way to centrally change PACKAGESITE without relying on each user to have properly config'd their individual shells? In the typical configuration only root can add packages, so just add it there. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
I'm curious, why does pkg_add -r point to the release snapshot of ports by default? Is the idea that a release is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with pkg_add -r? Seems to me it would be better to have pkg_add -r point to stable (which, if I understand things correctly, does get updated packages). -release packages have gone through an extensive period of testing with that release, so you have more confidence they will work. The up-to-date packages may not work, may not even be present on the FTP site, and in general are not suitable for users who just want a working system without having to fiddle with it. i.e. defaulting to the packages that came with the release is a conservative step that is appropriate for users who just want packages that work, and don't care about always having the latest versions. For the rest of you, you're going to be doing a lot more hands on admin anyway, so setting one env variable is not a heavy burden. Do the -release packages get updates for security (and only for security) reasons? I ask because I don't find any information about this on the FBSD webpages. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
Gueven Bay wrote: I'm curious, why does pkg_add -r point to the release snapshot of ports by default? Is the idea that a release is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with pkg_add -r? Seems to me it would be better to have pkg_add -r point to stable (which, if I understand things correctly, does get updated packages). -release packages have gone through an extensive period of testing with that release, so you have more confidence they will work. The up-to-date packages may not work, may not even be present on the FTP site, and in general are not suitable for users who just want a working system without having to fiddle with it. i.e. defaulting to the packages that came with the release is a conservative step that is appropriate for users who just want packages that work, and don't care about always having the latest versions. For the rest of you, you're going to be doing a lot more hands on admin anyway, so setting one env variable is not a heavy burden. Do the -release packages get updates for security (and only for security) reasons? I ask because I don't find any information about this on the FBSD webpages. No, we don't have the resources. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
In the last episode (Sep 04), Kris Kennaway said: Gary Affonso wrote: I'm curious, why does pkg_add -r point to the release snapshot of ports by default? Is the idea that a release is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with pkg_add -r? Seems to me it would be better to have pkg_add -r point to stable (which, if I understand things correctly, does get updated packages). -release packages have gone through an extensive period of testing with that release, so you have more confidence they will work. The up-to-date packages may not work, may not even be present on the FTP site, and in general are not suitable for users who just want a working system without having to fiddle with it. i.e. defaulting to the packages that came with the release is a conservative step that is appropriate for users who just want packages that work, and don't care about always having the latest versions. For the rest of you, you're going to be doing a lot more hands on admin anyway, so setting one env variable is not a heavy burden. Also, packages from the -stable directory may have different/conflicting dependencies compared to existing packages on your system. Imagine installing 6.2 before the x.org-7 update, then trying to pkg_add -r a package from the -stable directory that depends on an xorg-7 feature. pkg_add just isn't smart enough to realize that you really need to upgrade all of X, and will probably fail the install at some point. Ideally one would install 6.2 from a CD, select the packages they initially want, then pull an updated /usr/ports tree and update their system from that using their favorite tools from the ports/port-mgmt directory. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Philosophy of default pkg_add -r PACKAGESITE?
On Tuesday 04 September 2007 16:40:27 Dan Nelson wrote: Also, packages from the -stable directory may have different/conflicting dependencies compared to existing packages on your system. Imagine installing 6.2 before the x.org-7 update, then trying to pkg_add -r a package from the -stable directory that depends on an xorg-7 feature. pkg_add just isn't smart enough to realize that you really need to upgrade all of X, and will probably fail the install at some point. The same applies to a 6.2-STABLE before x.org-7 update, no difference there. It's not about port dependencies, it's about base-system dependencies. It doesn't happen often that within a minor release update a library gets a version bump, but binary incompatibilities may still occur. For -RELEASE you are expected to upgrade from source. Typical behavior being that ports only get upgraded when portaudit reports them unsafe. -- Mel People using reply to all on lists, must think I need 2 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Philosophy of default pkg_add -r PACKAGESITE?
Here's one thing I've never quite understood about FreeBSD and I was hoping somebody could provide some enlightenment... I've got 6.2-release installed. By default (as you all probably know) pkg_add -r fetches packages from the release directory: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release Now here's where it gets weird for me. If I understand the FreeBSD release methodology , that release is a frozen-in-time snapshot of a particular release (6.2 in my case) that gets no future updates. As we move farther and farther beyond a particular releases debut-date, that snapshot (and the packages it contains) gets increasingly stale. Do I have that right? If I do, it seems to me that the absolute first thing I should do after installing a release version would be to change where pkg_add -r is sourcing packages from. Either to current if I like to live on the edge or stable if I want to be a more conservative. I'm curious, why does pkg_add -r point to the release snapshot of ports by default? Is the idea that a release is well-tested and that any deviation from that (even security or bug-fix changes) is an unknown that new users need to be shielded against when grabbing packages with pkg_add -r? Seems to me it would be better to have pkg_add -r point to stable (which, if I understand things correctly, does get updated packages). And how does one go about *permanently* changing the pkg_add -r target. You can set the PACKAGESITE variable in the shell which will work on a user-by-user basis but isn't there a way to centrally change PACKAGESITE without relying on each user to have properly config'd their individual shells? I know a lot of thought has gone into the current system so I'm thinking that these questions are due to the fact that I'm just not grok'ing something important about the philosophy behind all this. Any help would be greatly appreciated. - Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade and packagesite
Hi people I am trying to upgrade my gtk20 and i do the following #setenv PACKAGESITE ftp://ftp1.freebsd.org/pub/FreeBSD/ports/i386/packages-5-current/ and then #portupgrade -PP gtk and this is what happens fetch: ftp://ftp1.freebsd.org/pub/FreeBSD/ports/i386/All/gtk-2.4.9_1.tbz fetch is tryin to download the packages from an incorrect path What am i doing wrong? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
