Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Jan 2017 01:45:56 +0200
From:      Arto Pekkanen <isoa@kapsi.fi>
To:        freebsd-pkg@freebsd.org
Subject:   Re: pkg : Undefined symbol "openat"
Message-ID:  <dc0ffcc2-f40b-8572-c4d0-dc4a74368b04@kapsi.fi>
In-Reply-To: <4dcb4c97-9b17-1e12-bb75-79f2a9624596@FreeBSD.org>
References:  <15974fd9b76-4ea4-3d956@webprd-m20.mail.aol.com> <5976c0fc-e9a4-bf70-a5cf-b063bbe849ce@kapsi.fi> <4dcb4c97-9b17-1e12-bb75-79f2a9624596@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--j5JBRk6JOtB47X5kAriv8re4BM3tklmtm
Content-Type: multipart/mixed; boundary="dmXpsUsuiXpUv7nbnnWB4EBGn4jXBIumN";
 protected-headers="v1"
From: Arto Pekkanen <isoa@kapsi.fi>
To: freebsd-pkg@freebsd.org
Message-ID: <dc0ffcc2-f40b-8572-c4d0-dc4a74368b04@kapsi.fi>
Subject: Re: pkg : Undefined symbol "openat"
References: <15974fd9b76-4ea4-3d956@webprd-m20.mail.aol.com>
 <5976c0fc-e9a4-bf70-a5cf-b063bbe849ce@kapsi.fi>
 <4dcb4c97-9b17-1e12-bb75-79f2a9624596@FreeBSD.org>
In-Reply-To: <4dcb4c97-9b17-1e12-bb75-79f2a9624596@FreeBSD.org>

--dmXpsUsuiXpUv7nbnnWB4EBGn4jXBIumN
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Yes.

Each release branch is supported for 2 years by ports, after which all
kinds of problems become apparent, first problem being not able to
install binary packages compiled for newer release. If the 2 year
support period is not enough, then one must compile everything from
ports, and later put their own time and money into maintaining a
collection of patches for the ports that happen to stop compiling. The
team of people working on the project is too small in number to put
enough man hours into maintaining a 2+ year LTS branch with separate
ports tree.

In general, there should be no reason to lock into a specific obsolete
release. The regressions between releases are pretty insignificant
compared to the increasing amount of man hours needed to work around
ports compilation problems on an obsolete release.

On 7.1.2017 13:20, Matthew Seaman wrote:
> On 07/01/2017 08:46, Arto Pekkanen wrote:
>> Why not just upgrade to the supported release 10.3?
>=20
> True, this is the best way forwards.  However for people that cannot,
> for whatever reasons, do that straight away, they should be able to
> maintain their systems reasonably well.  Except that they will have to
> do themselves a lot of what is done communally by the project for the
> supported versions.
>=20
>> You are just asking for trouble trying to run software on an obsoleted=

>> base system version.
>=20
> In this case, with openat(2) being in libc in 10.3 and successors, but
> not in 10.1, there will be an increasing disparity between software
> compiled for 10.3 and trying to run on a 10.1 system.  So you'ld have t=
o
> build your own packages.
>=20
> Even so, as the ports no longer supports earlier than 10.3, you'll find=

> various compile problems edging in.  Those you can workaround by locall=
y
> patching your ports tree.  pkg(8) itself is known to compile and work o=
n
> OS versions back to 8.x.
>=20
> In short: it's a lot less effort just to upgrade.
>=20
> 	Cheers,
>=20
> 	Matthew
>=20
>=20
>=20

--=20
Arto Pekkanen


--dmXpsUsuiXpUv7nbnnWB4EBGn4jXBIumN--

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

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

iF4EAREIAAYFAlhxfbcACgkQTBivhqtJa26P2QEAg27aX3aH3q+CN9gjfoWfidol
vRj32zUJWN/kP4VBOtgBAK+e0tMxilLx6rqbR/UXp4YSsII8G7QIeGIQJNZ/6jb8
=jed8
-----END PGP SIGNATURE-----

--j5JBRk6JOtB47X5kAriv8re4BM3tklmtm--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dc0ffcc2-f40b-8572-c4d0-dc4a74368b04>