Date: Wed, 16 Nov 2011 08:52:10 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: Recent ports removal Message-ID: <4EC379BA.1060800@infracaninophile.co.uk> In-Reply-To: <4EC3724F.4030006@FreeBSD.org> References: <20111109124325.17efc0d1.stas@deglitch.com> <20111109222435.GD92221@azathoth.lan> <20111110110637.GA3514@hades.panopticon> <4EBCC587.10701@FreeBSD.org> <20111111100708.GA24126@hades.panopticon> <20111111124012.3ec48cb3.stas@deglitch.com> <20111111213817.GB8896@lonesome.com> <4EBD9E6F.3040708@delphij.net> <4EBDA077.5070105@FreeBSD.org> <4EC2B720.4000605@infracaninophile.co.uk> <4EC3724F.4030006@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig63ECDE6EF196F387472C482F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 16/11/2011 08:20, Doug Barton wrote:
> On 11/15/2011 11:01, Matthew Seaman wrote:
>> On 11/11/2011 22:23, Doug Barton wrote:
>>>> By its
>>>>> nature, deprecated ports tends not to be updated for long time, por=
t
>>>>> tools like portmaster, portupgrade will not even see it because no
>>>>> PORTREVISION bump happen.
>>
>>> portmaster -L will warn you about ports marked
>>> DEPRECATED/FORBIDDEN/IGNORE/BROKEN if you run it against an updated
>>> ports tree. One area where we actually can improve here is to also pu=
t
>>> this information in the INDEX. I have an idea for that, just haven't
>>> been able to put the time into making it happen.
>>
>> How about something like the attached? Rather than adding to the INDE=
X,
>> this appends DEPRECATED, FORBIDDEN, IGNORE, BROKEN and EXPIRATION_DATE=
>> values to pkg-message, creating one if the port doesn't already have i=
t.
>=20
> Won't work for my use case, which is 'portmaster -L --index-only'
Orthogonal to your use case: adding this sort of stuff to the INDEX is a
good idea too. Not everyone uses portmaster though. Also changing the
format of the INDEX has ramifications with various 3rd party software
that uses it, so it's going to be some effort to get it all sorted and
debugged. (BTW. Very happy to code up any proposed experimental INDEX
formats in my FreeBSD::Portindex modules or receive patches.)
The change I propose here is fairly minimal, and it should ensure that
any user of ports or packages sees notification through mechanisms that
already exist. Since they will see this at the point they install a
deprecated port -- coupling that with bumping PORTREVISION at the point
the port is deprecated should bring such changes to the attention of
users in time for them to raise any objections / provide fixes etc.
In fact, as I think about it this morning, another idea is this sort of
mechanism could be used to notify users of unmaintained ports and ask
for volunteers to maintain them.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig63ECDE6EF196F387472C482F
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.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7DecEACgkQ8Mjk52CukIyLOACcDUFxS8egVYo/bpODsyAXMqGO
FnQAoIpqoNk9sb92EWj9Wt8KIZp3zkQe
=bfVT
-----END PGP SIGNATURE-----
--------------enig63ECDE6EF196F387472C482F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC379BA.1060800>