Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Doug Barton wrote: Miroslav Lachman wrote: I don't know if it is well known / documented somewhere in portmaster, but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long options This is why all of the ports tools should be in the ports tree. :) I just added the fix to the svn version of portmaster, if you can confirm that it works I'll add it to the port immediately. I was not aware of this issue, and apparently you're the first person to test package support on a release this old. Thank you, both for the testing and the bug report. It is not working - pkg_add on 6.3 has no option for Install the package without fetching and installing dependencies. I mean, there is no long nor short option for this, so this portmaster's functionality cannot be easily ported to 6.3. That's why I suggest to disable packages support on FreeBSD = 6.3 as it cannot work this way. pkg_add will always install dependencies on this old version. 6.3 pkg_add options usage: pkg_add [-vInrfRMSK] 7.2 pkg_add options usage: pkg_add [-viInfFrRMSK] According to man pkg_add on 6.4, there are needed options http://www.freebsd.org/cgi/man.cgi?query=pkg_addapropos=0sektion=0manpath=FreeBSD+6.4-RELEASEformat=html But not on 6.3 http://www.freebsd.org/cgi/man.cgi?query=pkg_addapropos=0sektion=0manpath=FreeBSD+6.3-RELEASEformat=html I think you don't need to spend a lot of time to solve this for 6.3 as it's Estimated EoL is January 31, 2010 ;) Maybe something like this can be enough: if [ ! `uname -r | egrep -q ^(5|6\.[0-3])` ]; then echo Packages options are not supported on your OS version exit fi And one question - is it really mandatory to use --local-packagedir=/usr/ports/packages if I want to install locally available packages from standard path /usr/local/packages/All? Yes. Shouldn't it be default behavior? IMO, no. I think that the vast majority of FreeBSD users just want to be able to fetch packages and have them installed. Without --local-packagedir portmaster is trying to fetch it from FTP: Package and/or archive not found at: http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/; and doesn't look at the local directory: There is no valid package to install, building port instead This is the desired behavior. OK, I can live with it. :) I was asking it because somebody can use NFS mounted /usr/ports from build machine and then all packages are located in /usr/local/packages/All and packages should be installed from this location only (not fetched from FreeBSD FTP). Is there a simple way to disable fetching packages from remote site and use local packages only? (something better than fake PACKAGEROOT?) Anyway, thank you for packages support in portmaster! Now I am waiting for more general scripting hooks such as BEFOREDEINSTALL and AFTERINSTALL and then portmaster will have all features I need! :o) Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Miroslav Lachman wrote: It is not working - pkg_add on 6.3 has no option for Install the package without fetching and installing dependencies. I mean, there is no long nor short option for this, so this portmaster's functionality cannot be easily ported to 6.3. That's why I suggest to disable packages support on FreeBSD = 6.3 as it cannot work this way. pkg_add will always install dependencies on this old version. Well that sucks. You're right, I'll have to add a warning for this issue. Thanks again for letting me know. I think you don't need to spend a lot of time to solve this for 6.3 as it's Estimated EoL is January 31, 2010 ;) Yeah, if only all FreeBSD users upgraded before the version they are using went EOL. :) OK, I can live with it. :) I was asking it because somebody can use NFS mounted /usr/ports from build machine and then all packages are located in /usr/local/packages/All and packages should be installed from this location only (not fetched from FreeBSD FTP). I added support for --local-packagedir to accommodate just this kind of configuration, but I still hold that it will be the exception rather than the rule, and that portmaster should be optimized for the majority of users. Is there a simple way to disable fetching packages from remote site and use local packages only? (something better than fake PACKAGEROOT?) Well I have --always-fetch now, I suppose I should add --never-fetch. That's QED. Anyway, thank you for packages support in portmaster! Now I am waiting for more general scripting hooks such as BEFOREDEINSTALL and AFTERINSTALL and then portmaster will have all features I need! :o) So help me line up support to get that feature done. :) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Doug Barton wrote: Howdy! I'm very excited to announce that what I hope to be the final version of the new portmaster with package support is now available for testing. I've done quite a bit of regression testing myself, but the last time I posted about the beta version several people were kind enough to give it a go and I got several really good suggestions. It would be really great if more users could give this version a try before I commit it to the actual port. You can find the information on accessing the svn version at http://dougbarton.us/portmaster-proposal.html [...] Hi Doug, I gave it a try, but no luck :) I tried portmaster --local-packagedir=/usr/ports/packages -P python26-2.6.2_3 and got error message: === Currently installed version: python26-2.6.2_3 === Port directory: /usr/ports/lang/python26 === Gathering dependency list for lang/python26 from ports === No dependencies for lang/python26 === Starting build and/or install for lang/python26 === === All dependencies are up to date === Checking package repository for latest available version === Available package (python26-2.6.4) matches the ports tree === Creating a backup package for old version python26-2.6.2_3 === Package saved to /usr/ports/packages/portmaster-backup pkg_delete: package 'python26-2.6.2_3' is required by these other packages and may not be deinstalled (but I'll delete it anyway): python-2.6,2 === Installing package pkg_add: illegal option -- - usage: pkg_add [-vInrfRMSK] [-t template] [-p prefix] [-P prefix] [-C chrootdir] pkg-name [pkg-name ...] === A backup package for python26-2.6.2_3 should be located in /usr/ports/packages/portmaster-backup === Installation of python26-2.6.4.tbz (lang/python26) failed === Aborting update I don't know if it is well known / documented somewhere in portmaster, but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long options (--no-deps --force), there is only -f, but no -i. If it can't be worked around, than packages support on FreeBSD 7 should be completely disabled. Tested in jailed FreeBSD 6.3-RELEASE-p5 with portmaster Version 2.15 And one question - is it really mandatory to use --local-packagedir=/usr/ports/packages if I want to install locally available packages from standard path /usr/local/packages/All? Shouldn't it be default behavior? Without --local-packagedir portmaster is trying to fetch it from FTP: Package and/or archive not found at: http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/; and doesn't look at the local directory: There is no valid package to install, building port instead Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Miroslav Lachman wrote: I don't know if it is well known / documented somewhere in portmaster, but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long options This is why all of the ports tools should be in the ports tree. :) I just added the fix to the svn version of portmaster, if you can confirm that it works I'll add it to the port immediately. I was not aware of this issue, and apparently you're the first person to test package support on a release this old. Thank you, both for the testing and the bug report. And one question - is it really mandatory to use --local-packagedir=/usr/ports/packages if I want to install locally available packages from standard path /usr/local/packages/All? Yes. Shouldn't it be default behavior? IMO, no. I think that the vast majority of FreeBSD users just want to be able to fetch packages and have them installed. Without --local-packagedir portmaster is trying to fetch it from FTP: Package and/or archive not found at: http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/; and doesn't look at the local directory: There is no valid package to install, building port instead This is the desired behavior. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
