Compatability with FreeBSD Ports [debian package tools]

walt wa1ter at myrealbox.com
Wed Aug 17 18:28:26 PDT 2005


> <4303571D.9050306 at xxxxxxxxxxxxx> <43036a16$0$739$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200508171711.j7HHBPi1021543 at xxxxxxxxxxxxxxxxxxxx>
In-Reply-To: <200508171711.j7HHBPi1021543 at xxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 14
Message-ID: <4303e43a$0$740$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 69.234.178.54
X-Trace: 1124328506 crater_reader.dragonflybsd.org 740 69.234.178.54
Xref: crater_reader.dragonflybsd.org dragonfly.users:3871

Matthew Dillon wrote:
>  ...Every time I have ever used portupgrade, the result has
>    been a completely broken system.  Every time.

Are you suggesting that YOU are a typical user???  I don't
think so!

I've had a few problems over the years, but far fewer than
I've had with the pkg_chk function of pkgsrc.  (I have never
thought that pkg_chk is even a close rival to portupgrade,
however.)

But -- the problem of package management and package building are
two separate topics (I believe).





More information about the Users mailing list