Is there a "best practice" for automated updating large number of interdependant ports? I keep my ports tree up-to-date, and sometimes I wish to install applications that depend on a newer version of an existing one, and fail. My current example is gnome. Recently, whatever I want to install requires gnome2.8 - how to update the giant list of gnome libs & apps? portupgrade -r? (but on what package?) What about ports that have dialog boxes which require user intervention?
Hi Ivan, Tuesday, December 7, 2004, 4:47:23 PM, you Cannot open file "C\TXT COOKIES\reply-en.txt":> Is there a "best practice" for automated updating large number of > interdependant ports? I keep my ports tree up-to-date, and sometimes I > wish to install applications that depend on a newer version of an > existing one, and fail.> My current example is gnome. Recently, whatever I want to install > requires gnome2.8 - how to update the giant list of gnome libs & apps? > portupgrade -r? (but on what package?)portupgrade -arR should be good...> What about ports that have dialog boxes which require user intervention?i don't know exactly, you have to watch and see what's happening.. -- Best regards +----------==/\/\==----------+ FreeBSD | DanGer <danger@wilbury.sk> | (__) The | DanGer@IRCnet ICQ261701668 | \\\'',) Power | http://danger.homeunix.org | \/ \ ^ To +----------==\/\/==----------+ .\._/_) Serve [ If idiots could fly this place would be an airport. ]
Quoth Ivan Voras on Tue, Dec 07, 2004 at 16:47:23 +0100> Is there a "best practice" for automated updating large number of > interdependant ports? I keep my ports tree up-to-date, and sometimes I > wish to install applications that depend on a newer version of an > existing one, and fail.portupgrade is what you want. Please, please, please do read the man page and understand what it tells you. Also, you should check the archives for a script I posted sometimes ago (fairly recently). -- yann@kierun.org -=*=- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041207/9ace8825/attachment.bin
## Ivan Voras (ivoras@fer.hr):> Is there a "best practice" for automated updating large number of > interdependant ports? I keep my ports tree up-to-date, and sometimes I > wish to install applications that depend on a newer version of an > existing one, and fail.portupgrade works in most cases, but...> My current example is gnome. Recently, whatever I want to install > requires gnome2.8 - how to update the giant list of gnome libs & apps?Not in this case. Check /usr/ports/UPDATING 20041107: : Do NOT use portupgrade(1) to update your GNOME 2.6 desktop to 2.8 Gruss, Christoph -- Spare Space
Hello,> Is there a "best practice" for automated updating large number of > interdependant ports? [..]> What about ports that have dialog boxes which require user intervention?you can use /usr/local/etc/pkgtools.conf to tell portupgrade which options to use when upgrading a certain port. I usually check the makefile of ports I want to install for necessary defines and set these together with "BATCH=YES" in pkgtools.conf, then use portinstall to install the port and check if it honors the BATCH=YES. Wolfgang
On Dec 7, 2004, at 12:38, Wolfgang Zenker wrote:> you can use /usr/local/etc/pkgtools.conf to tell portupgrade which > options > to use when upgrading a certain port. I usually check the makefile of > portsWhen using portupgrade(1), are Makefile.local files consulted?