Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Mar 2017 11:09:15 +0100
From:      Mathieu Arnold <mat@FreeBSD.org>
To:        Chris Wells <freebsd@chriswells.io>, freebsd-ports@freebsd.org
Subject:   Re: Using Quarterly Ports Branches
Message-ID:  <1801a9f5-48c1-0b24-0436-84dad8d6594a@FreeBSD.org>
In-Reply-To: <d73b7041-4333-16ba-3e40-12a9c302f64f@chriswells.io>
References:  <d73b7041-4333-16ba-3e40-12a9c302f64f@chriswells.io>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--jaV9VrEWUHHvmWibf7UcLqkwEIG9IaQfe
Content-Type: multipart/mixed; boundary="B9lUD5wtWdjGLg7v9DVG65CXSUtxxbRwq";
 protected-headers="v1"
From: Mathieu Arnold <mat@FreeBSD.org>
To: Chris Wells <freebsd@chriswells.io>, freebsd-ports@freebsd.org
Message-ID: <1801a9f5-48c1-0b24-0436-84dad8d6594a@FreeBSD.org>
Subject: Re: Using Quarterly Ports Branches
References: <d73b7041-4333-16ba-3e40-12a9c302f64f@chriswells.io>
In-Reply-To: <d73b7041-4333-16ba-3e40-12a9c302f64f@chriswells.io>

--B9lUD5wtWdjGLg7v9DVG65CXSUtxxbRwq
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Le 03/03/2017 =C3=A0 05:01, Chris Wells a =C3=A9crit :
> A few questions: If I switch from HEAD to a quarterly ports branch,
> should I "rm -r /usr/ports/*" before checking out the quarterly branch
> from SVN? If so, should I do the same every time I migrate to a newer
> branch (e.g., moving from 2017Q1 to 2017Q2)? I believe it makes sense
> when reverting to an older branch like HEAD to quarterly, but I'm
> hoping it's unnecessary when moving forward. Any other directories
> that should be cleaned for a first-time change to quarterly ports or
> subsequent quarterly migrations?

Mmm, if you are using svn, I do not think you ever need to remove
/usr/ports:

$ svn co https://svn.freebsd.org/ports/head ports
[blah]
$ cd ports
$ svn info|grep URL
URL : https://svn.freebsd.org/ports/head
Relative URL: ^/head
$ svn switch ^/branches/2016Q4
[blah]
$ svn info|grep URL
URL : https://svn.freebsd.org/ports/branches/2016Q4
Relative URL: ^/branches/2016Q4
$ svn switch ^/branches/2017Q1
[blah]
$ svn info|grep URL
URL : https://svn.freebsd.org/ports/branches/2017Q1
Relative URL: ^/branches/2017Q1

For svn switch to really work, you do have to make sure you did not
change files in the ports tree.

> Would it be possible to "simply" create a symlink at
> https://svn.freebsd.org/ports/branches/quarterly that always points to
> whatever the current quarterly branch is? That way, everyone who wants
> to use quarterly packages/ports wouldn't have to worry about
> constantly switching the ports branch on every system they manage. A
> side benefit would be that packages and ports can share the
> terminology and meaning for their quarterly branch. Bonus points:
> change pkg and ports to have a CURRENT symlink pointed to HEAD and a
> STABLE symlink pointed to the latest quarterly branch so the names are
> more in sync with the base system's branch names.

Currently, all our tools working automatically with the quarterly
branches do this before any run:

latest_branch=3D$(svn ls https://svn.freebsd.org/ports/branches/|sed -ne
'/^2.*Q./s|/$||p'|tail -1)

All you'd need to do before running svn update would be to run:

svn switch ^/branches/$(svn ls
https://svn.freebsd.org/ports/branches/|sed -ne '/^2.*Q./s|/$||p'|tail -1=
)

and it would automagically switch to the new branch when a new branch
happens.

> If the symlink would work and easy enough to manage, it would be a
> great portsnap default in the base system to match pkg. The icing on
> the cake would be a persistent local setting to tell portsnap what
> branch to use so the commands to fetch/update the ports tree are
> consistent whether using HEAD or a branch.

The problems with symbolic links, is that they do not work on all
filesystems.


--=20
Mathieu Arnold



--B9lUD5wtWdjGLg7v9DVG65CXSUtxxbRwq--

--jaV9VrEWUHHvmWibf7UcLqkwEIG9IaQfe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJYuUDNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz
QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IFi0P/3Q+qUZ0tWspakpmqpRHlkkc
zPSG9xjSIHR4CkxUyH709cHOxBv614YwxApvVO3IdkwLpD2kRiD6GA/mTR9zIbC0
BDwmzVhVlItaXPppyJqiECXWHOcvpvMmruey5f5l4VTqIxoLIaJEdtNiL4w+e+Qg
kJtZiWryU6Sn45t2eA4M0laJFbvGLCKalOMKEjrPj+r7C0E4TlfZ6oNXtbKDctrX
NyCiPJC2HIL70iHezV+ylT4HD2SoDozhAvsGkK7TrOw9/QZBuCAeAE1iH6Qts9D4
fI6r4zmakL5tRF7m7Hf52ouW4laZZZSVPfQp+CYj7XFpx7+oNC966MvkfUJ/jLuT
Q9bpWuDQAVMPvdGdn/oo3o3gaQg3BeTh6JWXMNLi6JBEzDnhiqL3MwztLtRdTg6D
QZQzBifjus0k+xvpNEJhjxG+9unTiv36Nx+vYF9+Som2Qm4HVaz4Nh1yXuqBsko4
wuQQ/LCBxrfwJTqaJqCKahV6AwNnyhHghP8NcP/Q0x2jl2rwq3rUBGM61vnBR5wn
izam2LagxUYxgD8PzcojkF+mcPponevI4Da0orlhXi5VNHb9NfgtlVhSdmEGN0p+
gTUU2M3Z0gfqXIZPF24O5JVMAceOUCT21l5bjLrftb2ZM7Njf+XZ7IDtZd1BZ/U7
WzH+QoC0OeJqg0UhJb+m
=4cFD
-----END PGP SIGNATURE-----

--jaV9VrEWUHHvmWibf7UcLqkwEIG9IaQfe--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1801a9f5-48c1-0b24-0436-84dad8d6594a>