On Tue, Feb 13, 2007 at 12:07:29PM +0000, Jesse Scott wrote:
> Markus Schatzl wrote:
> >On Mon, 12 23:23 , Marc Espie wrote:
> >
> >>As far as possible, avoid working on -current stuff using a system whose
> >>uname still says 4.0. Even though we try to avoid it, *every release*
> >>a few ports (mostly gnu stuff, of course) uses hardcoded release numbers
> >>in the weirdest places, and we get breakages in the most stupid places.
> >>
> >
> >I probably missed something, but I guess these errors don't
> >really result from not updating:
> >
> >"/usr/ports/infrastructure/mk/modules.port.mk", line 31:
> >Malformed conditional ("" != "")
> >"/usr/ports/infrastructure/mk/modules.port.mk", line 31:
> >Malformed conditional ("" != "")
> >"/usr/ports/infrastructure/mk/modules.port.mk", line 54: if-less
> >endif
> >"/usr/ports/infrastructure/mk/modules.port.mk", line 54: Need an
> >operator
> >"/usr/ports/infrastructure/mk/bsd.port.mk", line 239: if-less
> >endif
> >"/usr/ports/infrastructure/mk/bsd.port.mk", line 239: Need an
> >operator
> >Fatal errors encountered -- cannot continue
> >
> I ran into the same thing. Once the system rebuilt I had to perform the
> dreadful pkg_delete -q /var/db/pkg/* since the ports built on 4.0 would
> not work on 4.1-beta.
I'm sorry to say, but you guys are completely clueless.
The commit to modules.port.mk that says you need to have a current 'make'
binary happened over a month ago, and it's just that: update source,
rebuild make, end of story.
My ports machine is happily updating stuff from 4.0-current to 4.1-beta,
and so far, I did not have to remove a single installed package.
