From owner-freebsd-ports@FreeBSD.ORG Tue Apr 9 17:12:36 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5A996A2A for ; Tue, 9 Apr 2013 17:12:36 +0000 (UTC) (envelope-from florent@peterschmitt.fr) Received: from peterschmitt.fr (peterschmitt.fr [5.135.177.31]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8B0A28 for ; Tue, 9 Apr 2013 17:12:35 +0000 (UTC) Received: from [192.168.0.23] (4ab54-4-88-163-248-31.fbx.proxad.net [88.163.248.31]) by peterschmitt.fr (Postfix) with ESMTPSA id 939964AB4A1 for ; Tue, 9 Apr 2013 19:12:36 +0200 (CEST) Message-ID: <1365527499.4106.2.camel@localhost> Subject: Re: Growing list of required(ish) ports From: Florent Peterschmitt To: FreeBSD Mailing List Date: Tue, 09 Apr 2013 19:11:39 +0200 In-Reply-To: References: <51622F44.3050604@FreeBSD.org> <1365441764.4112.1.camel@localhost> <51641315.3080704@bluerosetech.com> <1365526115.3607.6.camel@localhost> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-bP+U/qScJSaU1UEllDaG" X-Mailer: Evolution 3.6.4 Mime-Version: 1.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: florent+FreeBSD-ports@peterschmitt.fr List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2013 17:12:36 -0000 --=-bP+U/qScJSaU1UEllDaG Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le mardi 09 avril 2013 =C3=A0 13:03 -0400, Robert Simmons a =C3=A9crit : > > Hum, I didn't thought about that. So I think it would be possible to > > have a secondary =C2=AB branch =C2=BB for the distribution including so= mething > > like =C2=AB special ports =C2=BB which can be retrieved, built and mana= ged (for > > porters) quickly. > > > > Anybody think something like that is relevant and possible to do ? >=20 > One thing to note is that these parts of base are kept just about as > up-to-date as ports over in the HEAD branch. In the case of OpenSSH, > HEAD is way way more up to date than ports. These changes are also > fairly quickly MFC'd over to stable. The real hiccup is that these > changes don't dribble out of freebsd-update. I see. So you suggest to use -STABLE ? Because -RELEASE is aimed to stay as frozen (I mean stable and secured) as possible, it makes sens not to have updates. --=20 Florent Peterschmitt +33 (0)6 64 33 97 92 florent@peterschmitt.fr --=-bP+U/qScJSaU1UEllDaG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAABAgAGBQJRZEvLAAoJEMtO2Sol0IIm+o0H/1lFC2lKr12XCeAdUFWvOnc6 Td+9Gei//eojYOiEAjwxZ2A/kDrwGIo8YypmOQeiCXw9U1s0aIuhEoxGS/3CMGAp J0orHfuUZ8zsmgCSn8zkx1qW3VrExMsnJTv75NrkUvKQLP1Lnzt91E3p1VXH+I0H mGawpgTRZQGfKeLUnlm9H/sAH0RfD+lRvBbjB07KtBCfvzecZ0sC005xi184lNCt gS7Gp4fq99lCE/wZ2zj6xld+snNAvlW1ullDMq8GBZUO6c2JGK9g8km8UXDUXzlY wdx8st64gqqpPKP0hHpIh6wMSnfENnhBRNY4pQ4saxTb1KHNbRz0QfAfPFxTgUA= =SzkF -----END PGP SIGNATURE----- --=-bP+U/qScJSaU1UEllDaG--