Re: (cvsup newbie questions)
On Sat, 18 Dec 2004 21:09:00 -0600, Nikolas Britton [EMAIL PROTECTED] wrote: Joshua Tinnin wrote: Well, if you build a port with make options once, then it will remember your make options. Otherwise, you can enter make arguments in /etc/pkgtools.conf, although this only helps if you know what arguments the ports you're installing might need. What do you mean it remembers what make options I used... if I do a portupgrade it without setting MAKE_ARGS in pkgtools.conf it will remember my make options from the last time I built it? Also how to I make it unremember make options I don't want anymore? I don't know about that. If I want portupgrade to use custom make flags, I specify them in /usr/local/etc/pkgtools.conf. To remove options from a previous build, you can do: # rm /var/db/ports/portname/options Also, semi related, whats this Generating INDEX-5 - please wait.. thing and why does it take an hour for it to generate? The machine is building the ports collection INDEX-5 file from the make describe output of all of the ports. You can simplify this process by doing 'make fetchindex' after you cvsup each time. -- Joshua Lokken Open Source Advocate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (cvsup newbie questions)
On Monday 20 December 2004 06:08 am, Joshua Lokken [EMAIL PROTECTED] wrote: On Sat, 18 Dec 2004 21:09:00 -0600, Nikolas Britton [EMAIL PROTECTED] wrote: Joshua Tinnin wrote: Well, if you build a port with make options once, then it will remember your make options. Otherwise, you can enter make arguments in /etc/pkgtools.conf, although this only helps if you know what arguments the ports you're installing might need. What do you mean it remembers what make options I used... if I do a portupgrade it without setting MAKE_ARGS in pkgtools.conf it will remember my make options from the last time I built it? Also how to I make it unremember make options I don't want anymore? I don't know about that. If I want portupgrade to use custom make flags, I specify them in /usr/local/etc/pkgtools.conf. To remove options from a previous build, you can do: # rm /var/db/ports/portname/options IIRC, pkgtools.conf only works with the pkgtools apps, like portupgrade. I don't think it works with making the port from the tree itself (like if you cd to the folder and make install clean), but options you use in building it from the ports tree will be stored in /var/db/ports/portname/options, as mentioned above. This is what I meant by remembered. Also, semi related, whats this Generating INDEX-5 - please wait.. thing and why does it take an hour for it to generate? The machine is building the ports collection INDEX-5 file from the make describe output of all of the ports. You can simplify this process by doing 'make fetchindex' after you cvsup each time. Yes, although you should cd /usr/ports before you do that. I guess the way people are doing this now is cvsup ports, cd /usr/ports make fetchindex portsdb -u (this last step will be done automatically when it needs to be done, but you can do it anyway after a ports tree update). You can also use /usr/ports/sysutils/p5-FreeBSD-Portindex , which speeds up the process of making a new INDEX locally. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (cvsup newbie questions)
On Mon, 20 Dec 2004 08:13:05 -0800, Joshua Tinnin [EMAIL PROTECTED] IIRC, pkgtools.conf only works with the pkgtools apps, like portupgrade. I don't think it works with making the port from the tree itself (like if you cd to the folder and make install clean), but options you use in building it from the ports tree will be stored in /var/db/ports/portname/options, as mentioned above. This is what I meant by remembered. Yes, correct. Also, semi related, whats this Generating INDEX-5 - please wait.. thing and why does it take an hour for it to generate? The machine is building the ports collection INDEX-5 file from the make describe output of all of the ports. You can simplify this process by doing 'make fetchindex' after you cvsup each time. Yes, although you should cd /usr/ports before you do that. I guess the way people are doing this now is cvsup ports, cd /usr/ports make fetchindex portsdb -u (this last step will be done automatically when it needs to be done, but you can do it anyway after a ports tree update). You can also use /usr/ports/sysutils/p5-FreeBSD-Portindex , which speeds up the process of making a new INDEX locally. Ah, yes, it does help to be in /usr/ports when one runs 'make fetchindex'. -- Joshua Lokken Open Source Advocate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
Kevin Smith wrote: 1) is there a test utility that I can run that will tell me which cvsup mirror server will be fastest ? I did this the manual way by pinging a few and looking at the ave times coming back. There's a port out there called fastest_cvsup which is supposed to do exactly that. Personally I've never used it so I can't give any further comments. 2) If I do update (src-all) using 5.3-RELENG tag is my version still called 5.3-RELEASE ? - or is it now some new release of that (ie like 5.3.1 ?)...I guess my question is: Are all updates of 5.3-RELEASE source still called 5.3-RELEASE. If you use RELENG_5_3 tag, you'll get 5.3-RELEASE-pN where N is a number which increases with every security update. Right now you would get 5.3-RELEASE-p2. If you use RELENG_5, you'll get 5.N-STABLE, where N is a number which increases after every release from the RELENG_5 branch. Right now you would get 5.3-STABLE. 3) After my cvsup of the ports collection completes updating, is there any easy way to check which ports were updated ? Using portupgrade you can check which of the ports you have installed were updated. But again, since I personally don't use portupgrade, I can't give you any furhter details on that. There should be more than you want to know about it in the list archives. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
On Saturday 18 December 2004 01:20 am, Toomas Aas
[EMAIL PROTECTED] wrote:
Kevin Smith wrote:
1) is there a test utility that I can run that will tell me which
cvsup mirror server will be fastest ? I did this the manual way by
pinging a few and looking at the ave times coming back.
There's a port out there called fastest_cvsup which is supposed to do
exactly that. Personally I've never used it so I can't give any
further comments.
/usr/ports/sysutils/fastest_cvsup/ - It works well; it's very simple.
One way to use it is like this in a script (if you live in the US - if
not, change the country code flag for fastest_cvsup):
#!/bin/sh
# find fastest server
SERVER=`/usr/local/bin/fastest_cvsup -q -c us`
if [ ${SERVER} != ]; then
# update ports tree
/usr/local/bin/cvsup -h $SERVER /path/to/ports-supfile
fi
2) If I do update (src-all) using 5.3-RELENG tag is my version
still called 5.3-RELEASE ? - or is it now some new release of that
(ie like 5.3.1 ?)...I guess my question is: Are all updates of
5.3-RELEASE source still called 5.3-RELEASE.
If you use RELENG_5_3 tag, you'll get 5.3-RELEASE-pN where N is a
number which increases with every security update. Right now you
would get 5.3-RELEASE-p2.
If you use RELENG_5, you'll get 5.N-STABLE, where N is a number which
increases after every release from the RELENG_5 branch. Right now you
would get 5.3-STABLE.
3) After my cvsup of the ports collection completes updating, is
there any easy way to check which ports were updated ?
Using portupgrade you can check which of the ports you have installed
were updated. But again, since I personally don't use portupgrade, I
can't give you any furhter details on that. There should be more than
you want to know about it in the list archives.
/usr/ports/sysutils/portupgrade/ Portupgrade also works well, especially
in updating recursive dependencies. Most of the time, a port can easily
be updated without incident along with its dependencies by checking for
out-of-date ports:
# portversion -v | grep needs
And then upgrading:
# portupgrade -rR name-of-port
I use it all the time, as do quite a lot of other people. Here's an
excellent tutorial by Dru Lavigne:
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page=1
Check out the rest of her FreeBSD articles here:
http://www.onlamp.com/pub/ct/15
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
On Dec 18, 2004, at 12:43 AM, Kevin Smith wrote: Thanks for the tips. For the moment, I'm leaving the OS sources alone and I'm updating the ports collection because my goal is to update gnome to version 2.8. The OS seems to be fine - although I'm sure there are additional bug fixes I can benefit from - but I'm a little scared to go through the build kernel/world thing right now - especially since everything is running nicely. (I have not had the OS crash in the 2 months since I've installed it - it has run continously -yet my linux 2.6 installation crashed regularly). I do have a few additional questions... 1) is there a test utility that I can run that will tell me which cvsup mirror server will be fastest ? I did this the manual way by pinging a few and looking at the ave times coming back. 2) If I do update (src-all) using 5.3-RELENG tag is my version still called 5.3-RELEASE ? - or is it now some new release of that (ie like 5.3.1 ?)...I guess my question is: Are all updates of 5.3-RELEASE source still called 5.3-RELEASE. 3) After my cvsup of the ports collection completes updating, is there any easy way to check which ports were updated ? In answer to your second question, the tag you're probably looking for is RELENG_5_3_RELEASE. This tag will maintain your 5.3 version number, but you'll get any bug fixes for that branch and security fixes. I would strongly recommend you use the RELENG_5_3 tag as this will allow you to do minor upgrades (from 5.3 to 5.3.1, for example). This will give you the best option, as you remain in the 5.3 branch, but you benefit from all the available improvements and bug fixes. HTH ___ Eric F Crist I am so smart, S.M.R.T! Secure Computing Networks -Homer J Simpson PGP.sig Description: This is a digitally signed message part
Re: cvsup newbie questions
On Friday 17 December 2004 21:11, Kevin Smith wrote: I'm interested in upgrading to gnome 2.8 (and possibly the newer releases of other applications) Gnome is one of the most troublesome metaports to upgrade. See http://www.freebsd.org/gnome/ for advice on upgrading. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (cvsup newbie questions)
Joshua Tinnin wrote: Well, if you build a port with make options once, then it will remember your make options. Otherwise, you can enter make arguments in /etc/pkgtools.conf, although this only helps if you know what arguments the ports you're installing might need. What do you mean it remembers what make options I used... if I do a portupgrade it without setting MAKE_ARGS in pkgtools.conf it will remember my make options from the last time I built it? Also how to I make it unremember make options I don't want anymore? Also, semi related, whats this Generating INDEX-5 - please wait.. thing and why does it take an hour for it to generate? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cvsup newbie questions
I'm interested in upgrading to gnome 2.8 (and possibly the newer releases of other applications)...I'm running the following version of freebsd: 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 In starting to learn cvsup, I'm trying to figure out what I need. The src-all collection seems like it is more than I want to update. Freebsd seems to be working fine on my system and I don't think that I want to upgrade any kernel or OS-related programs unless any applications that I would want depend on it. So, if I am just interested in the latest fixes/version for applications running on 5.3-Release, should I just upgrade the ports collection ? There is an example supfile in /usr/share/examples/cvsup/ports-supfile. Would this be the best configuration to use ? Also, when I do upgrade the ports tree, I'm assuming it will just upgrade the skeleton tree, correct ? Even if I do upgrade src-all, its not going to down load the .tar files for all the source code ? Thanks -K ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
On Fri, 17 Dec 2004 13:11:18 -0800, Kevin Smith [EMAIL PROTECTED] wrote: I'm interested in upgrading to gnome 2.8 (and possibly the newer releases of other applications)...I'm running the following version of freebsd: 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 In starting to learn cvsup, I'm trying to figure out what I need. The src-all collection seems like it is more than I want to update. Freebsd seems to be working fine on my system and I don't think that I want to upgrade any kernel or OS-related programs unless any applications that I would want depend on it. So, if I am just interested in the latest fixes/version for applications running on 5.3-Release, should I just upgrade the ports collection ? There is an example supfile in /usr/share/examples/cvsup/ports-supfile. Would this be the best configuration to use ? Also, when I do upgrade the ports tree, I'm assuming it will just upgrade the skeleton tree, correct ? Even if I do upgrade src-all, its not going to down load the .tar files for all the source code ? The src tree, which gets updated if you cvsup src-all is the source code to rebuild the operating system. The ports tree is, you're correct, the skeletons for building third party software, which includes gnome. If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean Go away on a vacation for the holidays, and when you get back, you _should_ have gnome built and installed, along with alot of goodies. As you're running 5.3-RELEASE, I don't believe most applications will require a system update, however, if you want to track security and critical patches to the OS, then you will want to cvsup the src tree (src-all) and use the RELENG_5_3 tag in your src-supfile. You should read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html HTH, -- Joshua Lokken Open Source Advocate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cvsup newbie questions
[snip] If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean Go away on a vacation for the holidays, and when you get back, you _should_ have gnome built and installed, along with alot of goodies. [snip] Make sure you set BATCH=yes or when you get home you will have a very annoying configuration menu on your screen asking you what you want to install. Good luck, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
Tom Connolly wrote: [snip] If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean there is also gnome2-lite, gnome2-fifth-toe, gnome2-office, and gnome2-power-tools Make sure you set BATCH=yes or when you get home you will have a very annoying configuration menu on your screen asking you what you want to install. set BATCH=yes where and what does it do with the optional make options, esp for meta ports? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cvsup newbie questions
Do a make BATCH=yes install clean Then it is set for all meta ports as well. I had to find this out the hard way. It took 3 days to install Gnome. I kept coming back to a menu configuration screen. Tom -Original Message- From: Nikolas Britton [mailto:[EMAIL PROTECTED] Sent: Friday, December 17, 2004 3:17 PM To: Tom Connolly Cc: 'Joshua Lokken'; 'Kevin Smith'; [EMAIL PROTECTED] Subject: Re: cvsup newbie questions Tom Connolly wrote: [snip] If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean there is also gnome2-lite, gnome2-fifth-toe, gnome2-office, and gnome2-power-tools Make sure you set BATCH=yes or when you get home you will have a very annoying configuration menu on your screen asking you what you want to install. set BATCH=yes where and what does it do with the optional make options, esp for meta ports? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
On Friday 17 December 2004 01:11 pm, Kevin Smith [EMAIL PROTECTED] wrote: I'm interested in upgrading to gnome 2.8 (and possibly the newer releases of other applications)...I'm running the following version of freebsd: 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 In starting to learn cvsup, I'm trying to figure out what I need. The src-all collection seems like it is more than I want to update. Freebsd seems to be working fine on my system and I don't think that I want to upgrade any kernel or OS-related programs unless any applications that I would want depend on it. Most of your questions have already been answered, but I thought it might be worth emphasizing a couple of things. First, unless you know exactly why you want to update only part of your sources, and you know exactly what those sources contain, then it's probably best to update all your sources. This is because a buildworld or build kernel could fail if you only update part of your sources and there are old versions of other files hanging around, or it could cause other issues even if it builds and installs. So, if I am just interested in the latest fixes/version for applications running on 5.3-Release, should I just upgrade the ports collection ? No, the ports collection is the collection of 3rd-party apps' Makefiles and patches - it just simplifies installing applications. To accomplish what you want, you should cvsup src-all with RELENG_5_3: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html , which, after a complete build, installworld and kernel: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html , should bring you up to patchlevel 2. This would be a good idea in general, as vulnerabilities in fetch and procfs have been fixed (you can subscribe to security alerts here: http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications ). You can also customize your kernel config file before you do this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html There is an example supfile in /usr/share/examples/cvsup/ports-supfile. Would this be the best configuration to use ? You should use that for updating your ports tree, which you can or should do before upgrading and/or installing apps. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page=1 http://www.onlamp.com/pub/a/bsd/2003/08/07/FreeBSD_Basics.html You can also install apps the traditional way, but the ports system is fairly reliable, although it has its quirks (which is to be expected with 12,000+ port entries). Also, when I do upgrade the ports tree, I'm assuming it will just upgrade the skeleton tree, correct ? Right, and the Makefiles and patches, but not the sources. Those can be fetched by themselves with various installation switches, and that's also done automatically when compiling and installing apps through ports. Even if I do upgrade src-all, its not going to down load the .tar files for all the source code ? It will download all the source code for FreeBSD, which you should do if you're going to rebuild for an update. You can keep it there afterwards for future upgrades or refinements (in /usr/src) unless space is a serious consideration. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
Whoops ... I misunderstood you ... On Friday 17 December 2004 02:58 pm, Joshua Tinnin [EMAIL PROTECTED] wrote: On Friday 17 December 2004 01:11 pm, Kevin Smith [EMAIL PROTECTED] wrote: snip So, if I am just interested in the latest fixes/version for applications running on 5.3-Release, should I just upgrade the ports collection ? No, the ports collection is the collection of 3rd-party apps' Makefiles and patches - it just simplifies installing applications. So, yes, if you're just interested in fixes for apps, then update the ports collection. Still, I recommend updating to the latest sources for any RELEASE, as most of the time the fixes are truly important for most users, and they won't disrupt your system other than the actual building and installing (well, if it can possibly be avoided, but in this case you won't notice any difference). Also, once you have the source, then updating with src-all with your RELEASE tag will only update critical fixes, not all the sources over again. It's also possible to patch your system manually by fine-tuning the sources you want with cvsup and then just rebuilding that part, or without using cvsup at all (using patch(1)), but if you're not familiar with that, then start with updating the complete system through these steps (briefly): cvsup your source, mergemaster -p, buildworld, build kernel, install kernel, reboot into single user, installworld and mergemaster. It's a bit of a trick the first time if you're not familiar with it, but the handbook walks you through it, and it's not as scary as it might sound. Just do it exactly the way they say, and *don't skip anything*, and you should be fine. If not, you can always ask here. BTW, I personally recommend not using the -j switch when doing buildworld. The handbook warns that it's not supported, although plenty of people use it anyway and later come here with related problems, so it might save headaches if you don't mess with it until and unless you want to try it for testing. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
Tom Connolly wrote: Do a make BATCH=yes install clean Then it is set for all meta ports as well. I had to find this out the hard way. It took 3 days to install Gnome. I kept coming back to a menu configuration screen. Tom Yes I kinda guess that it was a make option (the small yes gave it away) but how does it know what make options I what compiled in? and the same for meta-ports, when there's crap loads of programs installed (gnome)? For example, how would it know that I wanted to build firefox with -O2 and newicons options? I'm guessing when installing a single port it would be easy to look at the make file and set the make options you want (like make FOOBAR=yes BATCH=yes install clean) but there's not much sense in doing that for a single port install, I don't understand how I would set the make options for a meta-port let alone even find them all with all the ports that get installed when doing meta ports, heck, on my computer alone theres 332 ports installed, I'm still trying to figure them all out so I can set them in portupgrades config file, how do I manage all this crap?? and on top of that I don't even know what 4/5th's of those ports are even for. and why can't we have statically linked (or what ever its called) so we don't have to install all these f'ing build and run time dependencies and have every thing linked to everything else, hard drive space is not an issue now a days? -Original Message- From: Nikolas Britton [mailto:[EMAIL PROTECTED] Sent: Friday, December 17, 2004 3:17 PM To: Tom Connolly Cc: 'Joshua Lokken'; 'Kevin Smith'; [EMAIL PROTECTED] Subject: Re: cvsup newbie questions Tom Connolly wrote: [snip] If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean there is also gnome2-lite, gnome2-fifth-toe, gnome2-office, and gnome2-power-tools Make sure you set BATCH=yes or when you get home you will have a very annoying configuration menu on your screen asking you what you want to install. set BATCH=yes where and what does it do with the optional make options, esp for meta ports? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
On Friday 17 December 2004 03:44 pm, Nikolas Britton [EMAIL PROTECTED] wrote: Tom Connolly wrote: Do a make BATCH=yes install clean Then it is set for all meta ports as well. I had to find this out the hard way. It took 3 days to install Gnome. I kept coming back to a menu configuration screen. Tom Yes I kinda guess that it was a make option (the small yes gave it away) but how does it know what make options I what compiled in? and the same for meta-ports, when there's crap loads of programs installed (gnome)? For example, how would it know that I wanted to build firefox with -O2 and newicons options? Well, if you build a port with make options once, then it will remember your make options. Otherwise, you can enter make arguments in /etc/pkgtools.conf, although this only helps if you know what arguments the ports you're installing might need. I'm guessing when installing a single port it would be easy to look at the make file and set the make options you want (like make FOOBAR=yes BATCH=yes install clean) but there's not much sense in doing that for a single port install, I don't understand how I would set the make options for a meta-port let alone even find them all with all the ports that get installed when doing meta ports, heck, on my computer alone theres 332 ports installed, I'm still trying to figure them all out so I can set them in portupgrades config file, how do I manage all this crap?? Well, I do understand, as there's a lot of stuff that gets installed with many meta-ports for dependency reasons that you probably don't need all that much, but some of it you do need. Some of it is just libraries, and others are applications that don't have any other purpose but to do something really simple, but many programs need it, while others are programming languages that some programs are written in. and on top of that I don't even know what 4/5th's of those ports are even for. and why can't we have statically linked (or what ever its called) so we don't have to install all these f'ing build and run time dependencies and have every thing linked to everything else, hard drive space is not an issue now a days? Well, that's an issue with the developers of those various ports and sometimes the committers, and I grant that the ports system isn't perfect, but, honestly, it's a good idea to at least be familiar with the purpose of what's installed on your system, even if you don't have it all memorized. Like you can do a pkg_info -a and read up on what you don't understand. Yes, there's a lot there (you don't have to read it all at once), but FreeBSD is also not necessarily meant to be used carelessly. What I mean is that, while it's frustrating sometimes to scrutinize all the ports in a meta-port, or even all the installed ports on your system, it's a good idea to know what's going on with your system, particularly before you make changes to it by installing software. - jt -Original Message- From: Nikolas Britton [mailto:[EMAIL PROTECTED] Sent: Friday, December 17, 2004 3:17 PM To: Tom Connolly Cc: 'Joshua Lokken'; 'Kevin Smith'; [EMAIL PROTECTED] Subject: Re: cvsup newbie questions Tom Connolly wrote: [snip] If you want to install the latest version of gnome, you should cvsup the ports tree (ports-all), then cd into the directory for the gnome meta-port (it builds gnome and alot of associated apps) and build it, like so: # cd /usr/ports/x11/gnome2 # make install clean there is also gnome2-lite, gnome2-fifth-toe, gnome2-office, and gnome2-power-tools Make sure you set BATCH=yes or when you get home you will have a very annoying configuration menu on your screen asking you what you want to install. set BATCH=yes where and what does it do with the optional make options, esp for meta ports? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup newbie questions
Thanks for the tips. For the moment, I'm leaving the OS sources alone and I'm updating the ports collection because my goal is to update gnome to version 2.8. The OS seems to be fine - although I'm sure there are additional bug fixes I can benefit from - but I'm a little scared to go through the build kernel/world thing right now - especially since everything is running nicely. (I have not had the OS crash in the 2 months since I've installed it - it has run continously -yet my linux 2.6 installation crashed regularly). I do have a few additional questions... 1) is there a test utility that I can run that will tell me which cvsup mirror server will be fastest ? I did this the manual way by pinging a few and looking at the ave times coming back. 2) If I do update (src-all) using 5.3-RELENG tag is my version still called 5.3-RELEASE ? - or is it now some new release of that (ie like 5.3.1 ?)...I guess my question is: Are all updates of 5.3-RELEASE source still called 5.3-RELEASE. 3) After my cvsup of the ports collection completes updating, is there any easy way to check which ports were updated ? Joshua Tinnin wrote: Whoops ... I misunderstood you ... On Friday 17 December 2004 02:58 pm, Joshua Tinnin [EMAIL PROTECTED] wrote: On Friday 17 December 2004 01:11 pm, Kevin Smith [EMAIL PROTECTED] wrote: snip So, if I am just interested in the latest fixes/version for applications running on 5.3-Release, should I just upgrade the ports collection ? No, the ports collection is the collection of 3rd-party apps' Makefiles and patches - it just simplifies installing applications. So, yes, if you're just interested in fixes for apps, then update the ports collection. Still, I recommend updating to the latest sources for any RELEASE, as most of the time the fixes are truly important for most users, and they won't disrupt your system other than the actual building and installing (well, if it can possibly be avoided, but in this case you won't notice any difference). Also, once you have the source, then updating with src-all with your RELEASE tag will only update critical fixes, not all the sources over again. It's also possible to patch your system manually by fine-tuning the sources you want with cvsup and then just rebuilding that part, or without using cvsup at all (using patch(1)), but if you're not familiar with that, then start with updating the complete system through these steps (briefly): cvsup your source, mergemaster -p, buildworld, build kernel, install kernel, reboot into single user, installworld and mergemaster. It's a bit of a trick the first time if you're not familiar with it, but the handbook walks you through it, and it's not as scary as it might sound. Just do it exactly the way they say, and *don't skip anything*, and you should be fine. If not, you can always ask here. BTW, I personally recommend not using the -j switch when doing buildworld. The handbook warns that it's not supported, although plenty of people use it anyway and later come here with related problems, so it might save headaches if you don't mess with it until and unless you want to try it for testing. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
