upgrading ports from 4.1 to 4.2

2007-09-09 Thread Chris
I will be upgrading my ports tree from 4.1-release to 4.2-release when 4.2 comes out. This is my first ports upgrade. So I was wondering if my action plan looks right: - backup my existing 4.1 /usr/ports directory - untar the 4.2 ports tgz file in /usr/ports - go to /usr/ports/path/to/applicatio

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Edd Barrett
On 10/09/2007, Chris <[EMAIL PROTECTED]> wrote: > - go to /usr/ports/path/to/application to update each application - do I need > to do this for each individual application I installed from the ports > tree? Is there any > automated way of doing this? Read about -u for pkg_add (man pkg_add). When

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Stuart Henderson
On 2007/09/10 16:13, Chris wrote: > - also is there any way to distinguish applications I installed from the > package list and applications I installed from the ports tree? No; ports just create packages. If you 'make install' this checks /usr/ports/packages/whatever/foo.tgz is up-to-date and b

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Stuart Henderson
On 2007/09/10 12:48, nicodache wrote: > package are nice, but hwo do they handle flavor ? for some applications, packages are built with various (at least the more popular) FLAVORs. for others, you need to build the packages from ports yourself. > because I installed a system without X, and each

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread nicodache
package are nice, but hwo do they handle flavor ? because I installed a system without X, and each time in try to install (by ports) a new software, it tries to compile it using X, and thus fails. are package compiled using standard choice, thus using X I don't have ? or are package built in a more

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Edd Barrett
On 10/09/2007, nicodache <[EMAIL PROTECTED]> wrote: > package are nice, but hwo do they handle flavor ? > because I installed a system without X, and each time in try to > install (by ports) a new software, it tries to compile it using X, and > thus fails. > are package compiled using standard choi

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread nicodache
not supported as in "we don't care if you have problem with it", or not supported as in "it will certainly end with a segfault" ? On 9/10/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > building from ports without X is not supported (including those > that don't need X to run).

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Markus Hennecke
nicodache schrieb: On 9/10/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: building from ports without X is not supported (including those that don't need X to run). > > not supported as in "we don't care if you have problem with it", or > not supported as in "it will certainly end with a segfa

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread Markus Hennecke
nicodache schrieb: ok. so you all advice me to install 4.2 with xbase. and with that, I can install packages/ports with no_x11, and things that needs X parts will work correctly ? I'll go for that :) You can install no_x11 packages without xbase AFAIR. But you can't build them from ports. G

Re: upgrading ports from 4.1 to 4.2

2007-09-10 Thread nicodache
ok. so you all advice me to install 4.2 with xbase. and with that, I can install packages/ports with no_x11, and things that needs X parts will work correctly ? I'll go for that :) On 9/10/07, Markus Hennecke <[EMAIL PROTECTED]> wrote: > nicodache schrieb: > > On 9/10/07, Stuart Henderson <[EMAIL