Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Aug 2020 23:51:05 +0200
From:      Mateusz Piotrowski <0mp@FreeBSD.org>
To:        Mike Clarke <jmc-freebsd2@milibyte.co.uk>, "ports@FreeBSD.org" <ports@freebsd.org>
Subject:   Re: [HEADS UP] Planned deprecation of portsnap
Message-ID:  <f096cd76-60fe-a396-1df8-d0b8d6f9a77a@FreeBSD.org>
In-Reply-To: <1601531.MsCH1bHPGx@curlew>
References:  <b920d0e6-72d3-b37c-e57e-6d027292e8db@FreeBSD.org> <5122e2d8-444c-3a76-038a-be84d38fc237@FreeBSD.org> <20200809172701.7af573b1@gumby.homeunix.com> <1601531.MsCH1bHPGx@curlew>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/11/20 9:39 PM, Mike Clarke wrote:
> On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote:
>
>
>> What I'd like to see is a simple way to update the ports tree to match
>> what was used to build the current packages in the repository.
> Something I've felt in need of for a long time, and suggested from time to time
> in the past.
>
> What we need is a pkg command which returns the revision number of the
> ports tree which was used to build the current repository. When provided with
> that information I could run "svnlite up -q -r $REV $PORTSDIR" to keep my ports
> and packages in sync.
>
I also think that would be great.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f096cd76-60fe-a396-1df8-d0b8d6f9a77a>