Date: Tue, 15 Apr 2014 08:12:53 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: marino@freebsd.org, Baptiste Daroussin <bapt@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r351326 - head/Mk Message-ID: <534D3055.3070406@FreeBSD.org> In-Reply-To: <534D2F2B.4030606@marino.st> References: <201404151249.s3FCnkvQ026905@svn.freebsd.org> <534D2D57.60001@FreeBSD.org> <534D2F2B.4030606@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XtiJVvUIVqmr4NhOqtbkXKdNfKLdCBf23 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 4/15/2014 8:07 AM, John Marino wrote: > On 4/15/2014 15:00, Bryan Drewery wrote: >> On 4/15/2014 7:49 AM, Baptiste Daroussin wrote: >>> Author: bapt >>> Date: Tue Apr 15 12:49:46 2014 >>> New Revision: 351326 >>> URL: http://svnweb.freebsd.org/changeset/ports/351326 >>> QAT: https://qat.redports.org/buildarchive/r351326/ >>> >>> Log: >>> Register deprecation and expiration in packages >>> >> >> This will require bumping PORTREVISION for DEPRECATED and EXPIRE_DATE >> changes, resulting in a 100% useless rebuild. >> >> It would be much better to not have this in the packages at all and on= ly >> in the repo. >=20 > I think this conclusion depends on individual interpretation. > Did the installed binary change? No, so no bump needed. Does the pkg > internal database contents change? yes. Does that require a bump? >=20 > That depends on how vital the information is. > If it's considered "nice to have" and people can live with it only > coming in when the PKGNAME changes, then no bump is required. If the > lack of transparency on DEPRECATION is considered a real issue (and sur= e > many people do believe this) then yes, a bump would be needed to get it= > visible. >=20 > We're only talking about 120 packages here, so the price is not very > high. My vote is to that if this helps binary package users see > deprecated packages clearly then it's worth the rebuild. >=20 > John >=20 What I'd like to do is have the build gather all deprecated information and put it into the repo metadata. Then a 'pkg update' will get the new deprecation information for that repository. Then the dates can be displayed at pkg upgrade and in periodic scripts. Keep in mind bumping the revision is also extra build/bandwidth for the builder, bandwidth/time for user, and they must reinstall it as well. All for metadata. Otherwise needing a PORTREV bump can lead to the user not knowing if it is forgotten. --=20 Regards, Bryan Drewery --XtiJVvUIVqmr4NhOqtbkXKdNfKLdCBf23 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTTTBVAAoJEDXXcbtuRpfPThoH/1OT4CiZO47IXkd+7xFjl0tA lqi6/AGRB/AbiaN0lakjJhTJTMkz3mwMqRLm0ILbVDNJZUmfheoKKYI4VT12Gcy3 72M/vdSU/wLERav/3EfTv9faRCcIoOYy+n6P6Sf2pkTfqiC7jG9YlFF9zDVMLAnV sPdPwGQu1PaJZonKVlYZ2VoaScKSD54i/IiBSF7qNg9as377JKzo4obl4Xpa6uJU g1x08SnUzXccGErpQPDcs+va132uDV79tzWPQj8i3u8w8Gv5dPUasnLoKZeVLoic XODiyax66w0E+S8fg3gm/4eNuA5xm01ZeMQhRBaEPGQM1oRakFJcFMlcd+Q4xwA= =BGuc -----END PGP SIGNATURE----- --XtiJVvUIVqmr4NhOqtbkXKdNfKLdCBf23--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?534D3055.3070406>