On Thu, Dec 23, 2004 at 10:24:05PM -0800, Michael C. Shultz wrote:
> On Thursday 23 December 2004 09:59 pm, Kris Kennaway wrote:
> > On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> > > >run make fetchindex not make fetch index from /usr/ports
> > >
> > > Out of curiosity, why is
On Fri, 24 Dec 2004 17:27, Michael C. Shultz wrote:
> > Because the way we used to do it required tremendous churn in the
> > CVS repository. And it was _still_ out of date.
>
> We in user land don't see that end of things :) Why does INDEX have to
> go into the CVS repository anyways? Guess that
On Fri, 24 Dec 2004 17:13, Mark Linimon wrote:
> There's really quite a bit of email in the mailing list archives
> about why this was done. The short summary is that in the short
> run there is some pain but in the long run this is a win for the
> project, and the users.
IMHO it would have been
On Thursday 23 December 2004 10:43 pm, you wrote:
> On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> > Way back when, I used to get the INDEX when running cvsup unless
> > I put it in the refuse file. Of coarse it was old and useless so
> > one was better off building their own INDEX. So why cant w
On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> Way back when, I used to get the INDEX when running cvsup unless
> I put it in the refuse file. Of coarse it was old and useless so one was
> better off building their own INDEX. So why cant we just receive the
> INDEX like we used to, but unlike
# cd /usr/ports && make index-> failure?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Thursday 23 December 2004 09:59 pm, Kris Kennaway wrote:
> On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> > >run make fetchindex not make fetch index from /usr/ports
> >
> > Out of curiosity, why isn't the index included in the update
> > normally?
>
> It changes dozens of t
On Thursday 23 December 2004 09:42 pm, Brian Behlendorf wrote:
> On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> > On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
> >> These days it is best to run make fetch index from /usr/ports
> >> after you've run cvsup rather than build INDEX-5
On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> >run make fetchindex not make fetch index from /usr/ports
>
> Out of curiosity, why isn't the index included in the update normally?
It changes dozens of times per day, and the deltas would be enormous.
Kris
pgpxowY2MltXM.pgp
On Thu, 23 Dec 2004, Michael C. Shultz wrote:
On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
These days it is best to run make fetch index from /usr/ports
after you've run cvsup rather than build INDEX-5 for yourself.
-Mike
correction:
run make fetchindex not make fetch index from
On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
>
> These days it is best to run make fetch index from /usr/ports
> after you've run cvsup rather than build INDEX-5 for yourself.
>
> -Mike
correction:
run make fetchindex not make fetch index from /usr/ports
__
- Original Message -
From: "Michael C. Shultz" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 23, 2004 8:50 PM
Subject: Re: portsdb and portupgrade causes errors
> On Thursday 23 December 2004 08:37 pm, whitevamp wrote:
> > i dont know weathere this place
On Thursday 23 December 2004 08:37 pm, whitevamp wrote:
> i dont know weathere this place to be posting this to or not .. if
> not point me in the right direction to go..
>
> i have just updated my system to 5.3 frrom 4.9 and now every time i
> goto run portsdb , or portupgrade iget the same error
i dont know weathere this place to be posting this to or not .. if not point
me in the right direction to go..
i have just updated my system to 5.3 frrom 4.9 and now every time i goto run
portsdb , or portupgrade iget the same error message.and i also have a nother
5.3 box that was a fresh ins
14 matches
Mail list logo
