Re: Updating the ports collection
On Tue, Oct 06, 2009 at 09:07:07PM -0400, Chris Hill wrote: On Wed, 7 Oct 2009, Olivier Nicole wrote: Hi Chris, The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? I cannot speak for postsnap, but for cvsup: csup works (almost?) the same as cvsup, and is in the base system nowadays. I used to install cvsup, but now I only install fastest_cvsup; it's just a utility to find the fastest server for you at the moment. Some may correct me, but I use a file that contains: *default tag=. *default host=cvsup2.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs *default delete use-rel-suffix *default compress ports-all I do the same, and run csup as: csup -g -h `/usr/local/bin/fastest_cvsup -Q -c us` /etc/supfile.ports You can set SUPHOST= `/usr/local/bin/fastest_cvsup -Q -c us` SUPFLAGS= -g in /etc/make.conf and save yourself some typing. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpgwSQSo6iuQ.pgp Description: PGP signature
Re: Updating the ports collection
2009/10/7 Daniel Bye freebsd-questi...@slightlystrange.org On Tue, Oct 06, 2009 at 09:07:07PM -0400, Chris Hill wrote: On Wed, 7 Oct 2009, Olivier Nicole wrote: Hi Chris, The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? I cannot speak for postsnap, but for cvsup: csup works (almost?) the same as cvsup, and is in the base system nowadays. I used to install cvsup, but now I only install fastest_cvsup; it's just a utility to find the fastest server for you at the moment. Some may correct me, but I use a file that contains: *default tag=. *default host=cvsup2.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs *default delete use-rel-suffix *default compress ports-all I do the same, and run csup as: csup -g -h `/usr/local/bin/fastest_cvsup -Q -c us` /etc/supfile.ports You can set SUPHOST= `/usr/local/bin/fastest_cvsup -Q -c us` SUPFLAGS= -g in /etc/make.conf and save yourself some typing. Dan you -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ the above way is good but this is the simplest as it requires no additional programs or editing csup -h cvsup.FreeBSD.org /usr/share/examples/cvsup/ports-supfile I use the following as its a bit faster csup -h cvsup.uk.FreeBSD.org /usr/share/examples/cvsup/ports-supfile you can obviously insert your own country code ___ 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
Updating the ports collection
The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? Q2: Is this explained in the handbook? If so, where? Thank you, Chris PS: I uses sysinstall to obtain the ports collection from the CD during OS install ___ 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: Updating the ports collection
Chris Stankevitz wrote: The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? You can use csup as explained in section 4.5.1. This will update the Ports Collection you installed from CD/DVD by fetching only the required newer files Or, you can use portsnap too like this: First time: portsnap fetch extract Subsequent times: portsnap fetch update If you are starting with an empty Ports tree (for example you skipped installing it from CD during sysinstall) portsnap will be faster than csup. (Note you can start with an empty tree and csup as well) Anytime you decide to switch from csup to portsnap, always perform an 'extract' Q2: Is this explained in the handbook? If so, where? In section 4.5 as you noticed already. Portsnap is also revisited in chapter 24: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html ___ 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: Updating the ports collection
On Tue, 06 Oct 2009 15:43:56 -0700 Chris Stankevitz cstankev...@toyon.com wrote: The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? I'd suggest that you don't use the tree from sysinstall, unless your intent is not to update the tree until the next release. If you use portsnap the tree gets overwritten with the extract, so you might as well not bother with the on-disk version. If you use csup then the steps are 1. Set the tag to match the port snapshot on the disc and run csup 2. Set the tag to . (the current tree) and run csup again Step 1 does nothing to the tree, but if you skip it you may end with some stale files left in your tree, which could cause serious problems. IMO this is more trouble than it's worth unless you have a dialup connection. ___ 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: Updating the ports collection
Hi Chris, The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? I cannot speak for postsnap, but for cvsup: - you re-run sysinstall and install cvsup from the CD (Configure/Packages/Net/CVSup) - or, since you installed the port tree, you go to /usr/ports/net/cvsup-without-gui and you make, make install, make clean Q2: Is this explained in the handbook? If so, where? Some may correct me, but I use a file that contains: *default tag=. *default host=cvsup2.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs *default delete use-rel-suffix *default compress ports-all You may change the default host accordingly. Then I use the command cvsup name_of_that_file Best, Olivier ___ 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: Updating the ports collection
On Wed, 7 Oct 2009, Olivier Nicole wrote: Hi Chris, The FreeBSD handbook section 4.5.1 describes several methods for obtaining the ports collection including CVSup, Portsnap, and sysinstall. Section 4.5.1 also describes how to update the ports collection, but only for the CVSup and Portsnap methods. Q1: How do I update the ports collection after using sysinstall to obtain it? I cannot speak for postsnap, but for cvsup: csup works (almost?) the same as cvsup, and is in the base system nowadays. I used to install cvsup, but now I only install fastest_cvsup; it's just a utility to find the fastest server for you at the moment. Some may correct me, but I use a file that contains: *default tag=. *default host=cvsup2.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs *default delete use-rel-suffix *default compress ports-all I do the same, and run csup as: csup -g -h `/usr/local/bin/fastest_cvsup -Q -c us` /etc/supfile.ports ...where /etc/supfile.ports is pretty much as above. In that case, it doesn't matter what default host is set to, since the -h option to csup overrides the default. The '-c us' part applies to me, but it might not for you; see the man page. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging | ] ___ 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
Updating and Ports
Hi all, I have heard people chattering occasionally about /etc/make.conf. In a few days, I will be updating from 6.2, and 6.3, to RELENGE_6_3 and am curious how I can use / modufy /etc/make.conf so that I dont need to install all my ports again. Which leads to the question: I just installed /usr/ports/archivers/unzip onto all the servers, when I update to RELENG_6_3, will I need to reinstall them all over again? Which leads back to the original question, can I modify /etc/make.conf so that all ports currenly install are re installed? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating and Ports
On Wed, Oct 01, 2008 at 04:15:20PM -0400, Grant Peel wrote:
Hi all,
I have heard people chattering occasionally about /etc/make.conf.
In a few days, I will be updating from 6.2, and 6.3, to RELENGE_6_3 and am
curious how I can use / modufy /etc/make.conf so that I dont need to install
all my ports again.
You only have to reinstall your ports if you change to another major
version, e.g. from 6.x to 7.x. For a change from 6.2 to RELENG_6_3 that
isn't necessary.
Editing make.conf will not in any way reinstall ports for you. What it
make.conf does is pass options to the 'make' program. Nothing
more. Options in make.conf can be global or only apply when make is
called from a specific directory:
- make.conf example -
# Global flag; documentation languages
DOC_LANG=en_US.ISO8859-1
# Flag specific to the cups port.
.if ${.CURDIR:M*/print/cups*}
CUPS_OVERWRITE_BASE=true
.endif
- make.conf example -
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpL50ftcdQ6s.pgp
Description: PGP signature
Experience and thoughts on updating all ports (was Updating all ports)
I just upgraded my laptop from kde 3.5.1 taking a shot at using portupgrade and/or portmanager. From my previous experience portupgrade has been greatly enhanced/simplified. portmanager builds a database that gives a great status report and identifies orphaned port/packages. IMO these packages compliment one another. The problems with these tools are largely (I think) not of their own making. They depend on the ports tree and/or packages to accurately define requirements and dependencies. OpenOffice, to name one package, does not do this. Further, if you run kde (and probably any other comparable desktop), the interactions of dependencies are hopelessly complex. If you do not stay 'reasonably' current, using these tools (even as good as they are now) is much more complex and takes longer that simply clearing things out and starting over. The PC-BSD project seems to address this issue by picking a working set of ports. In my case I upgrade when a have a spare moment or when kde is around a year old. I decided I would install and look at port manager first, mostly because of my previous (and outdated) experience with portupgrade. portmanager currently does not allow (or attempt) to use packages, so I also installed portupgrade. My plan of attack was to remove kde and OpenOffice and try to upgrade the remaining ports/packages. My next step was to use portmanager to remove the orphaned (leaf) ports. This is not a good plan because this does not (necessarily) yield the set of ports that the kde package requires, and some of the leaf ports were both up-to-date and later required. Currently my laptop has nothing on it except kde 3.5.6, openopenoffice 2.2.0 and gaim. This requires something in excess of 200 ports. Starting from a base more than a year out of date, the upgrade tools did not have a chance to work (easily). I ended up with 2.5 days of building and required a second pass to clean up some dependencies. I then installed the kde package and had to uninstall one or two ports because dependency conflicts. OpenOffice installed with no issues other than the package from the OpenOffice site did not require its dependencies all of which I had erroneously removed as leafs. For some, the above is a bit complex (if not daunting) and I certainly do not have enough resources to build kde and OpenOffice from scratch. that process would add at least a week to the time I spent building. For a desktop system either constructed from packages or that has not been updated for several months, I think a viable alternative is to clear things out and install from packages starting with your desktop. This takes about two hours after you are familiar with the process and assumes using twm which is built into Xorg. If Xorg needs updating that must be done from the console. Xorg takes just a few minutes if a current version is available on cdrom. Using portupgrade with the noexecute option will give a sense of how complex upgrading will be. In some cases I still find starting over to be a viable and easier option to portupgrade/portmanager. To me it has the advantage over PC-BSD of having a more current set of applications. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating all ports
Marc G. Fournier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Saturday, May 19, 2007 23:51:35 -0500 Jack Barnett [EMAIL PROTECTED] wrote: For /usr/ports I sync to just '.' (dot). Is that what I want? (I want just 'stable' ports, nothing bleeding edge). for /usr/src I sync to: RELENG_6 But my question, is there a way to go though and say let's rebuild any port that is newer (via sync) then one I current have? For example, if I build and install application FooBar-1.0.0 from the /usr/ports and the next week FooBar-1.0.7 is there a way to say yea, let's rebuild this instead of manually building it? Or at the very least, give me a list of changes on which applications need to be manually built. Install /usr/ports/ports-mgmt/portupgrade ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGT97n4QvfyHIvDvMRArgeAKDrbrgHfAQ5YNeky3kB2sn2d0TYjQCg4SQL +Cwq8SvFjLs1EHN7dD5UXDM= =nyhg -END PGP SIGNATURE- That will take care of 95% of all cases, but isn't intelligent enough to do things properly 5% of the time (packages move, dependencies change, etc). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating all ports
Jack Barnett wrote: For /usr/ports I sync to just '.' (dot). Is that what I want? (I want just 'stable' ports, nothing bleeding edge). for /usr/src I sync to: RELENG_6 But my question, is there a way to go though and say let's rebuild any port that is newer (via sync) then one I current have? You don't want to update only ports that are newer by date as some older ports may need to be rebuild to link to the newer version of dependencies. cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org smime.p7s Description: S/MIME Cryptographic Signature
Updating all ports
Jack Barnett writes: For /usr/ports I sync to just '.' (dot). Is that what I want? (I want just 'stable' ports, nothing bleeding edge). for /usr/src I sync to: RELENG_6 But my question, is there a way to go though and say let's rebuild any port that is newer (via sync) then one I current have? Check out the contents of /usr/ports/ports-mgmt. (I use portupgrade. Your mileage may vary.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating all ports
For /usr/ports I sync to just '.' (dot). Is that what I want? (I want just 'stable' ports, nothing bleeding edge). for /usr/src I sync to: RELENG_6 But my question, is there a way to go though and say let's rebuild any port that is newer (via sync) then one I current have? For example, if I build and install application FooBar-1.0.0 from the /usr/ports and the next week FooBar-1.0.7 is there a way to say yea, let's rebuild this instead of manually building it? Or at the very least, give me a list of changes on which applications need to be manually built. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Saturday, May 19, 2007 23:51:35 -0500 Jack Barnett [EMAIL PROTECTED] wrote: For /usr/ports I sync to just '.' (dot). Is that what I want? (I want just 'stable' ports, nothing bleeding edge). for /usr/src I sync to: RELENG_6 But my question, is there a way to go though and say let's rebuild any port that is newer (via sync) then one I current have? For example, if I build and install application FooBar-1.0.0 from the /usr/ports and the next week FooBar-1.0.7 is there a way to say yea, let's rebuild this instead of manually building it? Or at the very least, give me a list of changes on which applications need to be manually built. Install /usr/ports/ports-mgmt/portupgrade ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGT97n4QvfyHIvDvMRArgeAKDrbrgHfAQ5YNeky3kB2sn2d0TYjQCg4SQL +Cwq8SvFjLs1EHN7dD5UXDM= =nyhg -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
updating 6.1 ports
Hi, Since 6.2 is released, how can one update ports on 6.1? at leasst to the maximum possible updates that was available for 6.1 till it was released? Thankyou so much :-) Kind regards Siju ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: updating 6.1 ports
Hi Ports are not release-dependent. Just use the default ports-supfile and you'll get the most up-to-date ports tree, regardless of the release you're running. Firas On Friday 11 May 2007 15:31:09 Siju George wrote: Hi, Since 6.2 is released, how can one update ports on 6.1? at leasst to the maximum possible updates that was available for 6.1 till it was released? Thankyou so much :-) Kind regards Siju ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Re: updating 6.1 ports
On Fri, 11 May 2007 19:01:09 +0530 Siju George [EMAIL PROTECTED] wrote: Hi, Since 6.2 is released, how can one update ports on 6.1? at leasst to the maximum possible updates that was available for 6.1 till it was released? The ports tree isn't branched, so you should be able to use the most recent. Upgrading from ports is covered in the handbook. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating the ports index is slow, but system load is nil
Hi, Sometimes (not always) when I do a 'portupgrade', it takes _ages_ to update the ports index, without actually placing any noticeable load on the system. In ports/UPDATING, it says (of make index) This may take an undesirably long time.. That would be fine, *if it were doing any work*. I try to speed it up by reniceing all the processes I can pin down as belonging to the portupgrade (is there a recursive renice for child processes?), but it makes no difference. Here's a grab of top, after I've been staring at Updating the ports index ... Generating INDEX.tmp - please wait.. for about 10 minutes PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 65942 rich 1010 37396K 27732K select 0:01 4.18% 2.39% kdeinit 62156 rich 960 52072K 40144K select 0:04 1.69% 1.56% kontact 557 root 960 102M 48316K select 15:39 0.88% 0.88% Xorg 67154 root 8 -5 7304K 7180K wait 0:00 2.96% 0.54% make 67520 root 8 -5 928K 800K wait 0:00 3.00% 0.15% make notice that a) there's almost no load on the system b) I managed to catch some of the make's and renice them c) It didn't help These two makes soon disappeared from the top of the list, leaving only background processes. It doesn't have any open network connections, so I'm not waiting for a remote machine; it doesn't have any system load so I'm not waiting for processing; the hard disk is (largely) idle, so I'm not waiting for i/o, but I am still waiting! How can I make it stop messing around and get on with it? Thanks, Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating the ports index is slow, but system load is nil
Richard Bradley wrote: [ ... ] It doesn't have any open network connections, so I'm not waiting for a remote machine; it doesn't have any system load so I'm not waiting for processing; the hard disk is (largely) idle, so I'm not waiting for i/o, but I am still waiting! How can I make it stop messing around and get on with it? Try make fetchindex. Your analysis of CPU load is largely correct, but it's helpful to understand that top doesn't display reliable information for transient processes which disappear in a second. Also, your analysis of I/O loading is wrong: building the index is quite disk intensive, but it involves lots of very small transactions: take a look at iostat 5 and notice that the MB/s is tiny, but the tps # will be significant, and quite probably so will the CPU load as measured here. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating the ports index is slow, but system load is nil
try to fetch the ports index before running portupgrade. cd /usr/ports make fetchindex portupgrade ?port? On Wed, 2 Mar 2005 01:51:45 +, Richard Bradley [EMAIL PROTECTED] wrote: Hi, Sometimes (not always) when I do a 'portupgrade', it takes _ages_ to update the ports index, without actually placing any noticeable load on the system. In ports/UPDATING, it says (of make index) This may take an undesirably long time.. That would be fine, *if it were doing any work*. I try to speed it up by reniceing all the processes I can pin down as belonging to the portupgrade (is there a recursive renice for child processes?), but it makes no difference. Here's a grab of top, after I've been staring at Updating the ports index ... Generating INDEX.tmp - please wait.. for about 10 minutes PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 65942 rich 1010 37396K 27732K select 0:01 4.18% 2.39% kdeinit 62156 rich 960 52072K 40144K select 0:04 1.69% 1.56% kontact 557 root 960 102M 48316K select 15:39 0.88% 0.88% Xorg 67154 root 8 -5 7304K 7180K wait 0:00 2.96% 0.54% make 67520 root 8 -5 928K 800K wait 0:00 3.00% 0.15% make notice that a) there's almost no load on the system b) I managed to catch some of the make's and renice them c) It didn't help These two makes soon disappeared from the top of the list, leaving only background processes. It doesn't have any open network connections, so I'm not waiting for a remote machine; it doesn't have any system load so I'm not waiting for processing; the hard disk is (largely) idle, so I'm not waiting for i/o, but I am still waiting! How can I make it stop messing around and get on with it? Thanks, Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [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: Updating the ports index is slow, but system load is nil
On Wed, Mar 02, 2005 at 01:51:45AM +, Richard Bradley wrote: Hi, Sometimes (not always) when I do a 'portupgrade', it takes _ages_ to update the ports index, without actually placing any noticeable load on the system. In ports/UPDATING, it says (of make index) This may take an undesirably long time.. That would be fine, *if it were doing any work*. Building the index is disk bound, not CPU bound. If you have slow disks it will take a very long time to build. Fortunately most people don't need to build their own indices, as explained in other emails. Kris pgpQqmtfQt76T.pgp Description: PGP signature
RE: correct routine of updating installed ports?
# cvsup -g -L 2 supfile # portsdb -uU # pkgdb -F # port_version # portupgrade -a And what does make index actually do? Do I need it? You missed a step between cvsup and portupgrade. less /usr/ports/UPGRADING ... and read, to check out what will happen when certain ports are updated. Looks much the same as I how I do it. I dont do a portversion. You might want to create a portupgrade log with the -l switch on portupgrade. Then, after its complete check for failed entries i.e. those marked with ! or * so you can manually check out the problem Also, you may want to add a portsclean at the end to remove old distfiles etc. man portsclean will give all the relevant options. Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
correct routine of updating installed ports?
Just want to confirm if this is the correct routine to update the installed ports. # cvsup -g -L 2 supfile # portsdb -uU # pkgdb -F # port_version # portupgrade -a And what does make index actually do? Do I need it? Thanks for any input. --- Choy Kho Yee url: http://dotkoyi.infoseek.ne.jp/ blog: http://dotkoyi.blogspot.com/ There are only 10 types of people in the world, i.e. those who understand binary numbers and those who do not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
