Re: Upgrading a port....

2004-04-25 Thread Joshua Lokken
* Ralph M. Los <[EMAIL PROTECTED]> [2004-04-25 10:14]:
> Hi,
>   I currently have Samba 2.2.8a running.  I'd like to get up to
> the 3.0.x.x version, as I've heard there are significant advances in
> that version.  Can someone tell me if I do a 'make install' from the
> /usr/ports/net/samba-devel directory if it'll "upgrade" my current Samba
> 2.2.8a to 3.x.x.x?  If not, what will happen?  Also, how would I go
> about upgrading in that case?
 
Samba 2.2.8 and 3.x are separate; similar to FreeBSD4.x and 5.x, I
suppose.  You definitely want to check out portupgrade if you're wanting
to maintain software from the ports collection, but I'm afraid a

# portupgrade samba-2.2.8

will not get you the desired results.  Now, I
don't know if they're mutually exclusive, but you may want to install
Samba 3.x on another machine to test it first.  I use it here at home,
and yes the 3.x branch does introduce alot of functionality not found in
2.2.8.

-- 
Joshua

"Lousy, loveable dog." -- Homer Simpson

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Upgrading a port....

2004-04-25 Thread Lewis Thompson
On Sun, Apr 25, 2004 at 01:03:52PM -0400, Ralph M. Los wrote:
>   I currently have Samba 2.2.8a running.  I'd like to get up to
> the 3.0.x.x version, as I've heard there are significant advances in
> that version.  Can someone tell me if I do a 'make install' from the
> /usr/ports/net/samba-devel directory if it'll "upgrade" my current
> Samba 2.2.8a to 3.x.x.x?  If not, what will happen?  Also, how would I
> go about upgrading in that case?

No, that won't work.  Look at sysutils/portupgrade.

-lewiz.

-- 
I was so much older then, I'm younger than that now.  --Bob Dylan, 1964.

-| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |-


pgp0.pgp
Description: PGP signature


Upgrading a port....

2004-04-25 Thread Ralph M. Los
Hi,
I currently have Samba 2.2.8a running.  I'd like to get up to
the 3.0.x.x version, as I've heard there are significant advances in
that version.  Can someone tell me if I do a 'make install' from the
/usr/ports/net/samba-devel directory if it'll "upgrade" my current Samba
2.2.8a to 3.x.x.x?  If not, what will happen?  Also, how would I go
about upgrading in that case?

Thanks,

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  Ralph | Internet Systems & Security   +
+   Boundariez.com   | -"Specializing in Paranoia"-  +
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  ralph[!at]boundariez[dot!]com |  Never understimate the power +
+AIM: SekurityWizard | stupid people +
+ICQ: 2206039|in large groups+
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: upgrading a port which has had a name change

2003-01-13 Thread Lowell Gilbert
chip wiegand <[EMAIL PROTECTED]> writes:

> I have xmms installed - in port_info it is shown as
> xmms-esound-1.2.7_2
> but when I ran portupgrade xmms-esound it failed because it is no longer
> called xmms-esound, it has changed to xmms-1.2.7_3. How do I do a
> portupgrade in this situation? Do I have to uninstall the old version
> and install the new version?

Isn't that what the '-o' option for portupgrade is for?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



upgrading a port which has had a name change

2003-01-12 Thread chip wiegand
I have xmms installed - in port_info it is shown as
xmms-esound-1.2.7_2
but when I ran portupgrade xmms-esound it failed because it is no longer
called xmms-esound, it has changed to xmms-1.2.7_3. How do I do a
portupgrade in this situation? Do I have to uninstall the old version
and install the new version?
--
Chip

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message