Re: How are ports built now
--On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 Reinstalling autoconf-2.69 (direct dependency changed) Reinstalling automake-1.14 (direct dependency changed) Reinstalling bootstrap-openjdk-r351880 (needed shared library changed) Reinstalling curl-7.37.0 (options changed) Reinstalling dejavu-2.34_3 (options changed) Upgrading en-freebsd-doc: 43251,1 - 44807,1 Reinstalling gettext-0.18.3.1_1 (options changed) Reinstalling igor-1.431 (direct dependency changed) Reinstalling ja-font-ipa-00303_1 (direct dependency changed) Reinstalling libgcrypt-1.5.3_2 (direct dependency changed) Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed) Reinstalling libxcb-1.10_2 (direct dependency changed) Reinstalling libxslt-1.1.28_3 (direct dependency changed) Reinstalling mcrypt-2.6.8_1 (direct dependency changed) Reinstalling mkfontdir-1.0.7 (direct dependency changed) Reinstalling mysqltuner-1.3.0 (direct dependency changed) Reinstalling neon29-0.29.6_6 (direct dependency changed) Reinstalling p5-Carp-Clan-6.04 (direct dependency changed) Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed) Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed) Reinstalling p5-type1inst-0.6.1_5 (options changed) Reinstalling perl5.14-5.14.4_7 (options changed) Reinstalling php5-5.4.29 (options changed) Reinstalling php5-bz2-5.4.29 (direct dependency changed) Reinstalling php5-ctype-5.4.29 (direct dependency changed) Reinstalling php5-curl-5.4.29 (direct dependency changed) Reinstalling php5-dom-5.4.29 (direct dependency changed) Reinstalling php5-filter-5.4.29 (direct dependency changed) Reinstalling php5-hash-5.4.29 (direct dependency changed) Reinstalling php5-iconv-5.4.29 (direct dependency changed) Reinstalling php5-json-5.4.29 (direct dependency changed) Reinstalling php5-mbstring-5.4.29 (direct dependency changed) Reinstalling php5-mssql-5.4.29 (direct dependency changed) Reinstalling php5-mysql-5.4.29 (direct dependency changed) Reinstalling php5-openssl-5.4.29 (direct dependency changed) Reinstalling php5-pdo-5.4.29 (direct dependency changed) Reinstalling php5-phar-5.4.29 (direct dependency changed) Reinstalling php5-posix-5.4.29 (direct dependency changed) Reinstalling php5-session-5.4.29 (direct dependency changed) Reinstalling php5-simplexml-5.4.29 (direct dependency changed) Reinstalling php5-tokenizer-5.4.29 (direct dependency changed) Reinstalling php5-xml-5.4.29 (direct dependency changed) Reinstalling
Re: How are ports built now
Hi Paul, On 08/06/2014 16:20, Paul Schmehl wrote: I have this in my /etc/make.conf file: DISABLE_VULNERABILITIES=yes FORCE_PKG_REGISTER=yes WITH_PKG=yes This should read: WITH_PKGNG=yes to encourage the use of the new pkg tools. Thanks, Daniel. ___ 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: How are ports built now
On 6/8/14, 11:20 AM, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) [[stuff]] === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: [[different stuff]] The upgrade will require 426 MB more space 373 MB to be downloaded Clearly portmaster and pkg upgrade disagree on what work needs to be done. Do you have non-default port options configured? I believe the packages are all created with the default options, so that if you've installed everything from ports, and some of those ports with non-default options, your dependencies when upgrading with portmaster could end up looking different than when upgrading with pkg. ___ 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: How are ports built now
--On June 8, 2014 at 11:38:37 AM -0400 Kevin Phair phair.ke...@gmail.com wrote: On 6/8/14, 11:20 AM, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) [[stuff]] === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: [[different stuff]] The upgrade will require 426 MB more space 373 MB to be downloaded Clearly portmaster and pkg upgrade disagree on what work needs to be done. Do you have non-default port options configured? I believe the packages are all created with the default options, so that if you've installed everything from ports, and some of those ports with non-default options, your dependencies when upgrading with portmaster could end up looking different than when upgrading with pkg. Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On 2014-06-08 17:20, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 Reinstalling autoconf-2.69 (direct dependency changed) Reinstalling automake-1.14 (direct dependency changed) Reinstalling bootstrap-openjdk-r351880 (needed shared library changed) Reinstalling curl-7.37.0 (options changed) Reinstalling dejavu-2.34_3 (options changed) Upgrading en-freebsd-doc: 43251,1 - 44807,1 Reinstalling gettext-0.18.3.1_1 (options changed) Reinstalling igor-1.431 (direct dependency changed) Reinstalling ja-font-ipa-00303_1 (direct dependency changed) Reinstalling libgcrypt-1.5.3_2 (direct dependency changed) Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed) Reinstalling libxcb-1.10_2 (direct dependency changed) Reinstalling libxslt-1.1.28_3 (direct dependency changed) Reinstalling mcrypt-2.6.8_1 (direct dependency changed) Reinstalling mkfontdir-1.0.7 (direct dependency changed) Reinstalling mysqltuner-1.3.0 (direct dependency changed) Reinstalling neon29-0.29.6_6 (direct dependency changed) Reinstalling p5-Carp-Clan-6.04 (direct dependency changed) Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed) Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed) Reinstalling p5-type1inst-0.6.1_5 (options changed) Reinstalling perl5.14-5.14.4_7 (options changed) Reinstalling php5-5.4.29 (options changed) Reinstalling php5-bz2-5.4.29 (direct dependency changed) Reinstalling php5-ctype-5.4.29 (direct dependency changed) Reinstalling php5-curl-5.4.29 (direct dependency changed) Reinstalling php5-dom-5.4.29 (direct dependency changed) Reinstalling php5-filter-5.4.29 (direct dependency changed) Reinstalling php5-hash-5.4.29 (direct dependency changed) Reinstalling php5-iconv-5.4.29 (direct dependency changed) Reinstalling php5-json-5.4.29 (direct dependency changed) Reinstalling php5-mbstring-5.4.29 (direct dependency changed) Reinstalling php5-mssql-5.4.29 (direct dependency changed) Reinstalling php5-mysql-5.4.29 (direct dependency changed) Reinstalling php5-openssl-5.4.29 (direct dependency changed) Reinstalling php5-pdo-5.4.29 (direct dependency changed) Reinstalling php5-phar-5.4.29 (direct dependency changed) Reinstalling php5-posix-5.4.29 (direct dependency changed) Reinstalling php5-session-5.4.29 (direct dependency changed) Reinstalling php5-simplexml-5.4.29 (direct dependency changed) Reinstalling php5-tokenizer-5.4.29 (direct dependency changed) Reinstalling php5-xml-5.4.29 (direct dependency changed) Reinstalling php5-xmlreader-5.4.29 (direct dependency changed) Reinstalling php5-xmlrpc-5.4.29 (direct dependency
Re: How are ports built now
On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. ___ 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: How are ports built now
--On June 8, 2014 at 10:32:33 AM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
--On June 8, 2014 at 6:05:35 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-08 17:20, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 On possible issue between `pkg upgrade' and portmaster with an current ports tree is that some of the ports where updated between last wednesday and now. E.g pkgconf and the freebsd docs where updated after the last package build. [removed a bunch of lines] Is it possible that portmaster builds with NO_PORTDOCS or DOCS=off or similar? No. The port mail/pflogsumm has as only OPTIONS_DEFINE=DOCS, but `pkg upgrade' complains about changed options Reinstalling pflogsumm-1.1.5,1 (options changed) DOCS on/off could be a possible explanation for all the '(options changed)' updates. In general I accept the default options, which is to install docs and examples. There are very few cases where I do not do that. Here's what portmaster wants to build now: === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docbook-sgml Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 All of these ports fail to install individually. Unfortunately, I have to have ghostscript because I use ImageMagick for our forum. Otherwise I remove it. It's always been problematic during installs and upgrades. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On Sat, Jun 7, 2014 at 10:19 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Ah, ok. Sorry for the confusion. I'm still using portupgrade, and haven't used portmaster, so I have nothing to add about that. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. All I can say is follow this mailing list closely. There seems to be a lot of problems with the ports tree lately, it has made me lose some confidence in the ports tree. Now I only update when I absolutely have to. Good luck! -- Regards, Torfinn Ingolfsen ___ 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: How are ports built now
--On June 8, 2014 at 7:17:01 PM +0200 Torfinn Ingolfsen tin...@gmail.com wrote: On Sat, Jun 7, 2014 at 10:19 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Ah, ok. Sorry for the confusion. I'm still using portupgrade, and haven't used portmaster, so I have nothing to add about that. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. All I can say is follow this mailing list closely. There seems to be a lot of problems with the ports tree lately, it has made me lose some confidence in the ports tree. Now I only update when I absolutely have to. Me too. Between staging and the change to pkgng, everything is upside down. It seems FreeBSD is headed toward the dependency hell of Linux instead of the smooth running ports system we once had. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On Sun, 8 Jun 2014, Paul Schmehl wrote: --On June 8, 2014 at 10:32:33 AM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage I can't say how it will work, just pointing out that until variant packages are available, ports with default options that aren't as desired still have to be built locally. ___ 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: How are ports built now
Paul Schmehl pschmehl_li...@tx.rr.com writes: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Presumably it's a typo that you left out the -f option? Without that, you wouldn't have been rebuilding everything, and surely you would have noticed by now. ___ 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: How are ports built now
--On June 8, 2014 at 2:50:53 PM -0400 Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Paul Schmehl pschmehl_li...@tx.rr.com writes: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Presumably it's a typo that you left out the -f option? Without that, you wouldn't have been rebuilding everything, and surely you would have noticed by now. Yes, it's a typo. I've been typing -ad for so long now trying to fix the remaining problems that I left that off. I'm about to give up on the whole thing and switch to another OS. This is beyond frustrating. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On 08/06/2014 17:54, Paul Schmehl wrote: It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage Yes. You're absolutely right -- there is a combinatorial problem with port options. However there are three things that will help: * Sub packages. Many option settings just add some extra files to a or data package. With the plan to create sub packages -- ie. dividing up the files from a single software compilation into more than one binary package -- a significant proportion of that goes away. * The realization that we really don't need to build packages for all different possible combinations of options. Some option sets simply don't work. Others are for features that only a tiny minority of people would ever want. * The ports isn't going away. If you need a special set of options for a particular port, then you will still have the choice of building from source via the ports. Unlike many other packaging systems, the results of doing this will still be completely integrated with the packaging system, and you will be able to mix and match ports you compile yourself with binary packages from the repositories. Hopefully the necessity of adopting the third option can be minimized, although nothing is going to stop you doing that should you simply prefer to do so. Staging is one of the big pieces necessary to make this all work. It also has the interesting side effect that since everything is built as a package it makes it quite natural to build your own package sets and set up a package repository. If you've got more than one FreeBSD system to manage[*], then I can heartily recommend setting up a package building system and package repository. It's like night and day: you build off-line at your leisure in a clean environment with no fuss and no worries if things don't work entirely right first time -- you haven't affected anything of consequence, so you can just fix the problem and try again without downtime on important services. You can install exactly the software you'll be using on a test system and run it though all the QA you could want before deploying it live. The when it comes to doing the actually installation of packages on your live systems it takes only seconds of disruption, and you're done. poudriere(8) + pkg(8) really is the winning combination. Cheers, Matthew [*] Or even if you only have just the one. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: How are ports built now
[snip snipperdy snip] Olli, was it really necessary to quote all 236 (!) of those lines? AvW -- I'm not completely useless, I can be used as a bad example. pgpQMWtVlnLfC.pgp Description: PGP signature
Re: How are ports built now
Hi, On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I'm an oldtimer, having used the port building system for years. Recently I upgraded two servers to 8.4 and implemented the pkgng system. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. Is portmaster not the appropriate method for updating ports with pkgng? Are we forced to now go to binary packages only? I think you are a bit confused here. AFAIK, portmaster, portupgrade and so on are management tools for installing and upgrading ports. However, to update the ports tree on your machine (which is what you use when you are building from source) you need another tool. Supported versions of FreeBSD have the portsnap(8) command, which is used to update the ports tree. HTH -- Regards, Torfinn Ingolfsen ___ 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: How are ports built now
--On June 7, 2014 at 10:04:17 PM +0200 Torfinn Ingolfsen tin...@gmail.com wrote: Hi, On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I'm an oldtimer, having used the port building system for years. Recently I upgraded two servers to 8.4 and implemented the pkgng system. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. Is portmaster not the appropriate method for updating ports with pkgng? Are we forced to now go to binary packages only? I think you are a bit confused here. AFAIK, portmaster, portupgrade and so on are management tools for installing and upgrading ports. However, to update the ports tree on your machine (which is what you use when you are building from source) you need another tool. Supported versions of FreeBSD have the portsnap(8) command, which is used to update the ports tree. Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. I'm still trying to figure out what's wrong. I thought it might be some sort of conflict between the portmaster db and the pkgng db. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? Are we forced to now go to binary packages only? No, of course not. However, it might be that Portmaster cannot handle *installing* binary packages in the new format. I'm not sure because I let Portmaster build PKGNG-style binary packages and use PKGNG to install those on other jails/systems, but I seem to recall something along the lines of Portmaster not yet being able to use PKGNG-style binary package repositories. I might be way off here, though. AvW -- I'm not completely useless, I can be used as a bad example. pgptFlp6ncMA8.pgp Description: PGP signature
Re: How are ports built now
--On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How are ports built now
On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. -- Regards, olli ___ 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: How are ports built now
On 07 Jun 2014, at 23:16, olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. -- Regards, olli ___ 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 Did you put WITH_PKGNG=1 (or yes) Into your /etc/make.conf ? ___ 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