error in "make index"

[Michael C. Shultz]

On Friday 24 December 2004 12:51 am, Adam Weinberger wrote:
> Kris Kennaway wrote:
> > On Fri, Dec 24, 2004 at 03:38:56AM -0500, Adam Weinberger wrote:
> >>Mark Linimon wrote:
> >>>Sigh.  Already fixed.  A quick check of tonight's mailing list
> >>> would have confirmed that this has already been reported.  Please
> >>> re-cvsup and try again.
> >>>
> >>>I'm beginning to wonder if when we took INDEX out of the
> >>> repository we should have disabled the index target, or aliased
> >>> it to the fetchindex one.
> >>>
> >>>I would really advocate that most people move to "make fetchindex"
> >>>and only use "make index" if there is some pressing reason (local
> >>>non-standard ports installations, unusual and well-understood
> >>>make.conf options).
> >>
> >>I've already suggested this to knu, but it bears repeating here:
> >> I'd really really really strongly advocate portupgrade running
> >> 'make fetchindex' instead of 'make index'.
> >
> > The corresponding change was committed today.
>
> It seems that it only does so if you run 'portsdb -F' manually
> yourself. If you remove INDEX* and run 'portupgrade -a', it still
> attempts to build INDEX the 'make index' way.
>
> >>And frankly, I'd support having 'make fetchindex' run automatically
> >> by the ports build system if the ${PORTS_INDEX} file doesn't
> >> exist.
> >
> > That sounds like a good idea.
>
> Should I open a PR for it?
>
> # Adam

What if someone isn't connected to the internet? Probably shouldn't be 
done automatically during port builds because many people just build 
from a CD.

-Mike