Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 May 2009 08:51:38 +0300
From:      Ion-Mihai Tetcu <itetcu@FreeBSD.org>
To:        freebsd-ports@freebsd.org
Cc:        Ion-Mihai Tetcu <itetcu@FreeBSD.org>
Subject:   Re: custom PREFIX/LOCALBASE QA run
Message-ID:  <20090531085138.5bd9cc21@it.buh.tecnik93.com>
In-Reply-To: <20090531055601.7d7aacc2@it.buh.tecnik93.com>
References:  <20090531055601.7d7aacc2@it.buh.tecnik93.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/WmhS=M0kVl+VS1unW7rR8Rz
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sun, 31 May 2009 05:56:01 +0300
Ion-Mihai Tetcu <itetcu@FreeBSD.org> wrote:
On Sun, 31 May 2009 05:56:01 +0300
Ion-Mihai Tetcu <itetcu@FreeBSD.org> wrote:

> Hi,
>=20
>=20
> In the ongoing QA effort, the second QA Tinderbox - QATty - is
> currently doing a full run of the Ports Tree with PREFIX, LOCALBASE
> and X11BASE set to a custom directory. =20

Why should you care about custom PREFIX and LOCALBASE:
- because we claim we support it and we should put our money where our
  mouth is=20
- because it makes it possible to install eg. in ~/ eg. to test stuff
  before replacing the older version in LOCALBSE
- because it makes it easier to create plists
- because PCBSD's port-to-PBI converter needs it
- ...
=20
> The build is done with PT from 2009-05-28 18:03:14; I'll be probably
> updating it after each category is built.
>=20
> QATtyMails are sent to the maintainers (and other interested parties)
> for each failure (but not more often that 2 weeks), with links to the
> port status on QAT and PortsMon.
>=20
> Often fixing the errors is easy and requires a one-two lines
> modification of the port Makefile or a little patch. =20

A few hints:

- if the port fails with mtree errors then it's almost certain to have
  a hard-coded PREFIX=3D/usr/local in it; grep -R /usr/local WRKDIR should
  help. You can test your fix via `make PREFIX=3D/tmp/PORTNAME install`

- if it fails with configure_, linker_ or missing_header error then
  compare the log from QATty with the one from QAT; the differences in
  configure or build phase might prompt you in the right way; suspect
  either hard-coded /usr/local for -I and -L CFLAGS/CXXFLAGS or
  missing -I${LOCALBASE}/include -L${LOCALBASE}/lib and equivalents.
  You might also need to hint ./configure where to find libs from
  dependencies via some --with... (or patch the brain-dead configure
  script).

- make PREFIX=3D/tmp/PORTNAME LOCALBASE=3D/tmp/PORTNAME -V CONFIGURE_ENV -V=
 CONFIGURE_ARGS -V CFLAFS ....

- look in other BSDs (or Linux) repositories for fixes

- if you get stuck, try again :-) and if you're still stuck ask here
  for help

We would appreciate you telling us (eg. by replying to the QATtyMail)
that you work on a fix for a certain port in order to not duplicate the
effort.

Don't forget to push your patches upstream, there are others that will
benefit from them!


I've fixed all unmaintained ports that failed so far and a few
maintainers already submitted fixes for their ports which fixes I
committed.


It took a year+, and in to many cases tens of QATMails, me prodding or
going in and fixing ports to have a somewhat decent obeisance of
NOPORT*.

I'm not willing to wait that much for PREFIX/LOCALBASE problems to be
fixed. Current target is 6 months or 3 QATtyMails (so minimum 6 weeks)
after which we'll either fix it or I'll mark the port in question
BROKEN accordingly.

The only good reason I can see for a port not to obey PREFIX is if it's
a binary port; in this case: please try to get upstream vendor to
support custom PREFIX/LOCALBASE (via eg. env vars or .conf file, ...)
and please submit a PR explaining the problem with corresponding patch
attached.

That's 6 months because we need a few more runs in order to test ports
that depend on the currently broken ones; and because of available
hardware resources.

Speaking of hardware resources, QAT Restless Daemons are aching to
posses a few more machines, for other QA testing. If you or your
employer have a machine that idles and want to put it to good use
please contact me. Thank you!


Happy patching,

--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B

--Sig_/WmhS=M0kVl+VS1unW7rR8Rz
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iEYEARECAAYFAkoiGuoACgkQJ7GIuiH/oeV5JACdFa0a/kp0VAsTrn7XJYsQW3Dh
rfMAn3z8y0HQrRbP5vzEouxcEg6maxR/
=woJA
-----END PGP SIGNATURE-----

--Sig_/WmhS=M0kVl+VS1unW7rR8Rz--



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