epilogue said:
Just out of curiosity, is it incorrect to simply say that ports build
packages?
Yes.
Well, now I've received one explicit yes answer and one explicit no answer
to this question, leading me to believe that there might not be a clear
consensus even among experienced FreeBSD
Lowell Gilbert said:
If you think you see specific places to improve the documentation,
please write it up and submit it in a Problem Report. FreeBSD is,
after all, a volunteer project...;2~
That would probably be a better use of my time than grousing about it on a
mailing list, so I think I
On Wednesday 25 August 2004 09:28 am, Charles Ulrich wrote:
epilogue said:
Just out of curiosity, is it incorrect to simply say that ports build
packages?
Yes.
Well, now I've received one explicit yes answer and one explicit no
answer to this question, leading me to believe that there
Lowell Gilbert said:
In FreeBSD, a port is a third-party application ported to be built from
source on your system. A package is a pre-compiled binary of that port.
Once installed, they are both tracked (and removable) by the same database,
usually referred to as the package database. See the
Charles Ulrich wrote:
The phrase ports
build packages is a neat and efficient way of rectifying the
misunderstandings that can occur when trying to give a proper
explanation of FreeBSD package management.
Charles,
Thank you for concisely answering a burning question I didn't
know how to
On Tue, 24 Aug 2004 14:47:03 -0400 (EDT)
Charles Ulrich [EMAIL PROTECTED] wrote:
Lowell Gilbert said:
In FreeBSD, a port is a third-party application ported to be built
from
source on your system. A package is a pre-compiled binary of that
port. Once installed, they are both tracked (and
Charles Ulrich [EMAIL PROTECTED] writes:
Just out of curiosity, is it incorrect to simply say that ports build
packages?
No, packages are indeed built from ports.
That is, once a piece of software is installed with 'make install',
is it treated the same as any package that was
On Tue, Aug 24, 2004 at 12:13:31PM -0700, Jay O'Brien wrote:
Charles Ulrich wrote:
The phrase ports
build packages is a neat and efficient way of rectifying the
misunderstandings that can occur when trying to give a proper
explanation of FreeBSD package management.
Thank you for
Matthew Seaman [EMAIL PROTECTED] writes:
That phrase -- ports build packages is just so right on so many
levels. Except for the literal description of what actually happens.
It seems that a lot of the supposed confusion of novices comes from
the fact that we don't have a separate word to
Thanks to everyone who has been answering my questions over the past
several days (weeks) concerning installing and upgrading FreeBSD.
I am now going to try again. I am installing v. 4.8 on a server. This
server is to be a Postfix w/Courier IMAP server integrated into a
Linux-based network,
Curtis Vaughan writes:
Finally, while I'm reinstalling 4.8, I would like to know
something about the following.
It seems to me that cvsup is actually downloading the entire
repository of packages for FreeBSD. Is that really what one has
to do to perform an upgrade?
Cvsup
Curtis Vaughan writes:
Finally, while I'm reinstalling 4.8, I would like to know
something about the following.
It seems to me that cvsup is actually downloading the entire
repository of packages for FreeBSD. Is that really what one has
to do to perform an upgrade?
Cvsup
On 23 Aug, 2004, at 13:16, Robert Huff wrote:
Curtis Vaughan writes:
Finally, while I'm reinstalling 4.8, I would like to know
something about the following.
It seems to me that cvsup is actually downloading the entire
repository of packages for FreeBSD. Is that really what one has
to do to
Curtis Vaughan [EMAIL PROTECTED] writes:
I am now going to try again. I am installing v. 4.8 on a server.
This server is to be a Postfix w/Courier IMAP server integrated into a
Linux-based network, authentication centralized using PAM LDAP.
That's about it.
Now, some people might say,
Since I have reinstalled macosx (v 10.2) and upgraded to current v
10.2.8, i no longer can reach my man pages or many of my commands. on
startup of terminal i get message saying system cannot find manpath or
grep. I have tried to track down the problem, but can't seem to get
the system to
John Minter wrote:
Since I have reinstalled macosx (v 10.2) and upgraded to
current v 10.2.8, i no longer can reach my man pages or
many of my commands. on startup of terminal i get message
saying system cannot find manpath or grep. I have tried to
track down the problem, but can't seem to get
On Dec 12, 2003, at 06:35, John Minter wrote:
Since I have reinstalled macosx (v 10.2) and upgraded to current v
10.2.8, i no longer can reach my man pages or many of my commands. on
startup of terminal i get message saying system cannot find manpath or
grep. I have tried to track down the
17 matches
Mail list logo
