Date: Thu, 07 Mar 2013 12:54:58 +0100 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= <r.c.ladan@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: [HEADS UP] FreeBSD Ports tree has been tagged with RELEASE_7_EOL Message-ID: <51388012.8000309@gmail.com> In-Reply-To: <1UDYrv-0003UL-Ko@internal.tormail.org> References: <20130306171916.GA34145@freefall.freebsd.org> <1UDYrv-0003UL-Ko@internal.tormail.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/07/13 11:08, Jan Beich wrote:
> Thomas Abthorpe <portmgr-secretary@FreeBSD.org> writes:
>
>> - We do not require committers/maintainers to support 7.x, although ports
>> will need to be marked as BROKEN/IGNORE if they do not build/run.
>
> Why not add an entry to UPDATING and teach portsnap(8) about EOLTIME?
>
> # a sample text based on freebsd-update(8)
> if [ ${EOLTIME} -lt ${NOWTIME} ]; then
> echo
> cat <<-EOF
> WARNING: `uname -sr` HAS PASSED ITS END-OF-LIFE DATE.
> Any ports issues discovered after `date -r ${EOLTIME}`
> specific to your version may not be corrected.
> EOF
> return 1
> fi
>
> For one, not reading UPDATING pretty much guarantees running into an
> issue at some point anyway compared to not reading ports-announce@ list.
Adding a similar warning to bsd.port.mk was propopsed on the
freebsd-emulation list, at
http://lists.freebsd.org/pipermail/freebsd-emulation/2013-March/010463.html
Rene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51388012.8000309>