• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Adding/Removing Software under Freebsd

LuckyTaxi

Diamond Member
Normally I would go into the /usr/ports directory of the software and do a 'make deinstall'
Then I'm reading about 'pkg_remove' and 'pkg_add'

What is the difference, and what is the appropriate way to install new software.

Also how to go about updating software with a newer version.
 
Hi,

Generally, I only compile myself, from ports, if I have to (special optimizations, special libraries, etc.).
You can install a binary and it's dependencies using the -r (remote) command.

pkg_add -r programname

Here is what the FreeBSD guys have to say about ports, (pretty much what you do now)

FreeBSD handbook

and somebody else too

more info yet

and even more!

 
thx for the tip. 'pkg_add' requires the tar file in hand, while 'make install clean' will go fetch the files for you.
This is why I love freebsd. It took me 15 minutes to update PHP on my mandrake box today. damn dependencies!
 
This is why I love freebsd. It took me 15 minutes to update PHP on my mandrake box today. damn dependencies!

Perhaps you should install a distribution that actually does what you want then? Debian does auto-dependency fullfilling and you won't have to wait for it to compile.
 
good one...im itching to try it out. i hear good things about apt-get

However, i dont want to touch potato right now. i have this thing against old kernels.
it's running like 2.2 right? i like having the new stuff. besides, i dual boot and cant stand
the 8 gig limitation LILO puts on you with the older kernels.
 
When its done

Pretty much. It's frozen, but no date has been set so I wouldn't hold my breath. They have to wait for all 6-8 (some are just hoped for woody releases) ports to get working before a date can be set.

It did a http install of woody last night (XFS boot disks are woody only) and it worked great. I personally don't see a reason to wait.

Just saw your post about old kernels. woody is also slated for release with a 2.2 kernel, because they don't believe the 2.4 kernels are stable enough. You can run 2.4 kernels with no problem, but the CDs will have 2.2.something on it.

the 8 gig limitation LILO puts on you with the older kernels.

It has nothing to do with 2.2 kernels, it's a lilo/BIOS limitation. Using a newer lilo and 2.2 kernel won't be affected by the 1024 cylinder problem.
 


<< When its done

Pretty much. It's frozen, but no date has been set so I wouldn't hold my breath. They have to wait for all 6-8 (some are just hoped for woody releases) ports to get working before a date can be set.
>>



KDE developers use the "when its done" excuse. I heard that and loved it. Did you ever check out my dselect for Mac OS X link?

 


<< i just added cvsupit (and dependencies) with this

pkg_add -r cvsupit

look ma not local tar files 🙂
>>



Ill try it on OpenBSD next time I delve into ports. I never bothered with packages much because I like to add optimizations to some things.
 


<< It has nothing to do with 2.2 kernels, it's a lilo/BIOS limitation. Using a newer lilo and 2.2 kernel won't be affected by the 1024 cylinder problem. >>



So, if i were to download the stable version (Potato) I should be ok? I am tempted to download SID.
 
Back
Top