Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Jan 2016 07:53:16 +0000
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Unexpected dependencies of graphics/libGL
Message-ID:  <569DEB6C.5020109@FreeBSD.org>
In-Reply-To: <20160119063438.ca57c8a3bd8ba6781a58b040@ime.usp.br>
References:  <20160117031923.ce1f36547351bf07b6fff9a0@ime.usp.br> <20160117070715.1c33732b.freebsd@edvax.de> <20160117162018.964db3b1f2f2133242773e78@ime.usp.br> <20160117220247.69e6774f.freebsd@edvax.de> <20160118161235.GA92637@neutralgood.org> <20160119050806.cd08ca0687e76a4b09a701e3@ime.usp.br> <20160119062345.5402e98b.freebsd@edvax.de> <20160119063438.ca57c8a3bd8ba6781a58b040@ime.usp.br>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--mPRvjGbApSGsGJScR9rr8qknkMWKN4P7V
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 19/01/2016 06:34, Lu=EDs Fernando Schultz Xavier da Silveira wrote:
> Indeed. I avoid mixing ports and packages. In each jail I choose one
> method. But for the host I prefer ports.

Actually, it is no big deal to mix ports and packages, *so long as they
are built from compatible ports trees*.  That means similar ports tree
versions, make.conf settings and port options.  None of those has to be
identical, but the more changes you introduce along those lines the
greater the chance of problems.

One useful way of working is to make poudriere use /usr/ports as it's
default set of ports, eg:

% poudriere ports -l
PORTSTREE METHOD TIMESTAMP           PATH
default   svn    2016-01-18 16:40:49 /usr/ports

and make poudriere and direct compilation use the same options settings:

% ls -la /usr/local/etc/poudriere.d/options
lrwxr-xr-x  1 root  wheel  13 Dec 24  2012
/usr/local/etc/poudriere.d/options@ -> /var/db/ports

and synchronize the contents of /etc/make.conf and
/usr/local/etc/poudriere.d/make.conf

(Note: if you use package sets or some of the other more advanced
poudriere options, you may need to use some different filenames under
/usr/local/etc/poudriere.d -- it's all fairly obvious in practice though.=
)

With this setup, you can do an ad-hoc build of a port if you need it,
and be confident that it will interoperate with the packages installed
from your repo, given you did a 'poudriere bulk' and then a 'pkg
upgrade' after each update to /usr/ports.

	Cheers,

	Matthew



--mPRvjGbApSGsGJScR9rr8qknkMWKN4P7V
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQJ8BAEBCgBmBQJWnettXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC
QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATO0QQAKETr9pCDqXpVIrF4X2hDOqI
/vLSmMFVrgEVlKQ7Yd6oDIi47b0XXcmnuPxzP/MkC5o6EoZCs6hiylsD27WPoyb4
3whQmMK9eAeUO5XwKGnkZzjZjxukakP40hdERsdU+NIV9wb7Reji8LyLtnBLUlVb
3gASRzm9gooAAja43Fz9cOZ4oA19cbXiEhvPDoi/O0fIdgyUc04ncjKbfMfkguqq
8lHloJHpnCKQbxdk2yuaIKmqUEoBJiql/pWLWj7hwM38wS3Om6c2jRdb2EE5EsD9
d+rjI3n2s+R3zGgQodvzSvO+vqfrwa9XCWLgk+p3w6TXMjoG/NRa9k6VE29dck5E
oepfrn5zeRlGmXmcbeaKd7NQqj8llsvqi1bHis7RDapcB6RHIHufvi9R45ywY237
R3jwNl6oCP0rIh4I+dpzCgL/GeJSJD4t+F5saBI3jO+14BubRGlZMb+EMVr976t8
rxFpLJ9GmKOfhf7EB5mE+jU/oyUseyIJm+r4v0CfL5uqvMBegPqKKVwTBVooAUpb
tgmEbD538DXiljGChlV7cZUuhcL7BiYL0u33YSK//QdXubPNrQxd3DTvWz+Z6ffx
TbmZCHZGXBkjvrU+NVAkUqdGmGAlcL5tV33DceBIRTxdcKPCSmfjehwS9uG/eKJv
IiKNmCmkSR1QbTZOsEv0
=ip0n
-----END PGP SIGNATURE-----

--mPRvjGbApSGsGJScR9rr8qknkMWKN4P7V--



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