On 19/11/2012 04:51, Steve Kostecke wrote:
You don't. Just update the port to the current version of ntp-devel.
Doing so usually works unless there is a significant enough change in
the port codebase to "break" the port.
Here's how:
1. cd /usr/ports/net/ntp-devel
2. Edit the Makefile and updat
On 2012-11-18, David Taylor wrote:
> On 18/11/2012 00:27, Thomas Laus wrote:
>
>> The FreeBSD port maintainer is the one that keeps up with updating
>> the port when new versions become available.
>
> ... I guess I just have to wait if I use the portmaster route.
You don't. Just update the port
On 18/11/2012 07:49, Garrett Wollman wrote:
[]
And on FreeBSD you'd do it the exact same way as you do on GNU/Linux,
and with the same disadvantages (viz., inability to use the standard
package management tools to update or remove it).
-GAWollman
Thanks, Garrett, I can give that a try.
--
Chee
In article ,
David Taylor wrote:
>Thanks, Tom, I guess I just have to wait if I use the portmaster route.
> At least on Windows and Linux I now know how to compile the latest
>tarball archive.
And on FreeBSD you'd do it the exact same way as you do on GNU/Linux,
and with the same disadvantag
On 18/11/2012 00:27, Thomas Laus wrote:
On 2012-11-17, David Taylor wrote:
Pardon my ignorance, but with FreeBSD if I run:
# portmaster -a
# portmaster net/ntp-devel
I appear to get 4.2.7p304, which is not the latest version. Is there
something extra I should be doing to get the late
On 2012-11-17, David Taylor wrote:
> Pardon my ignorance, but with FreeBSD if I run:
>
># portmaster -a
># portmaster net/ntp-devel
>
> I appear to get 4.2.7p304, which is not the latest version. Is there
> something extra I should be doing to get the latest version, or am I
> reliant o
Pardon my ignorance, but with FreeBSD if I run:
# portmaster -a
# portmaster net/ntp-devel
I appear to get 4.2.7p304, which is not the latest version. Is there
something extra I should be doing to get the latest version, or am I
reliant on whoever updates the FreeBSD stuff?
I think thos
