Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Mar 2009 12:03:23 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        RW <rwmaillists@googlemail.com>
Cc:        ports@freebsd.org
Subject:   Re: portmanager modifying bsd.port.mk
Message-ID:  <1236618203.1680.20.camel@balrog.2hip.net>
In-Reply-To: <20090309143803.2d5ec944@gumby.homeunix.com>
References:  <49B41108.8060105@telenix.org> <20090308210404.3895216d@gumby.homeunix.com> <20090309143803.2d5ec944@gumby.homeunix.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-20RHPZuam/cl5ytoaqnl
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2009-03-09 at 14:38 +0000, RW wrote:
> I think this was probably intended for the list rather than me:
>=20
> On Mar 8, 4:04 pm, RW <rwmailli...@googlemail.com> wrote:
> > On Sun, 08 Mar 2009 14:40:08 -0400
> >
> > Chuck Robey <chu...@telenix.org> wrote: =20
> > > Here's the portmanager listing, maybe someone here can tell me
> > > what's causing portmanager to want to patch my bsd.port.mk, and why
> > > the patchfile should be so far off, and what might be the CORRECT
> > > way to fix this.  Oh, BTW, I run current, and keep myself that way
> > > via cvsup.. =20
> >
> > IIRC the patch was made so that when portmanager built a port, the
> > makefile would call back into  portmanager to let it modify the
> > dependencies. Portmanager had a major rewrite just before the
> >  original author had a row with some FreeBSD people and abandoned the
> > project. AFAIK the feature wasn't yet used, so it doesn't matter if
> > the patch doesn't apply since it's a null operation.
>=20
>=20
> I'm the original author of portmanager,  haven't done anything bsd
> related in a few years so memory is a bit vague.
> I think the patch was to correct a sorting problem with dependencies
> in freebsd make. I filed a pr against make
> and was assured there was no way it would ever approved so that patch
> is a work around.  If it is failing, isn't really
>  a big surprise, means something has changed in make finally.  Best
> solution I guess is to determine if make
> was fixed somewhere along the line, maybey look up the pr i filed
> agains make? if its fixed now, then remove the patch,
> if not, then someone who understands scripts needs to recut the
> patch.   I drive a semi for a living now and seriously
> doubt I'll ever take up programming again for lack of time, so very
> sorry I'm not able to provide more help with this problem.

Mike,

Thanks for the info.  Yes, bsd.port.mk changed about a year or so ago
now... portmanager still did what I needed it to do, so I just ignored
it.  I will try and find the old, PR and have a look.

thanks,

robert.

> Mike Shultz
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-20RHPZuam/cl5ytoaqnl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iEYEABECAAYFAkm1S9sACgkQM4TrQ4qfROPlSACfXyQwC65hWYgZ21B1P1+vRvcQ
1FMAmwVyr3NByAYAdBQJYDrzyrXKam6e
=LZ35
-----END PGP SIGNATURE-----

--=-20RHPZuam/cl5ytoaqnl--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1236618203.1680.20.camel>