Steve Kargl <s...@troutmask.apl.washington.edu> writes: > On Mon, Dec 04, 2017 at 11:49:30AM +0000, Alan Hicks wrote: > >> >> >> On 02/12/2017 17:28, Steve Kargl wrote: >> > On Sat, Dec 02, 2017 at 02:06:32PM +0100, Christian Ullrich wrote: >> >> * Steve Kargl wrote: >> >> >> > >> > Given that I asked about a specific revision number, it stands >> > to reason that I had already spent too much time wandering around >> > svnweb.freebsd.org. An entry needs to be added to ports/UPDATING >> > to state which revision turns on flavors and by extension neuters >> > all port management tools except poudriere. Four months from now >> > when users update a system finding that information by crawling >> > through svnweb.freebsd.org will be a challenge. >> > >> >> Your friend is subversion log search >> svn log --search FLAVORS svn://svn.FreeBSD.org >> >> r455205 | mat | 2017-11-30 15:33:29 +0000 (Thu, 30 Nov 2017) | 13 lines >> >> Generic FLAVORS work.
Another way to get the revision: $ svn blame /usr/ports/CHANGES | awk '/FLAVOR/ { rev=$1 } END { print rev }' 455205 > > This does not document the change in ports/UPDATING. FreeBSD > users have been told to check {src/ports}/UPDATING for 20+ > years. UPDATING is for individual POLA violations, CHANGES is for the framework, MOVED is for renames/deletions. For now flavors changed the way to install py* ports for non-default python version thus got an UPDATING entry. > A change that fundamentally changes the way users interact with ports/ > should document. That's an overstatement. Non-assisted builds (e.g. "make install") mostly work as before. _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"