From owner-freebsd-ports@FreeBSD.ORG Tue Apr 9 17:28:45 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4232E38C for ; Tue, 9 Apr 2013 17:28:45 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id C963CB6B for ; Tue, 9 Apr 2013 17:28:44 +0000 (UTC) Received: by mail-ea0-f173.google.com with SMTP id k11so2911827eaj.18 for ; Tue, 09 Apr 2013 10:28:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=Ep0JPqEfNYVtMXqIdHpIwObMxlQbP6j5Viai7S5MJH8=; b=f/9TL8eulMj0FUWPXsH51KWjyjZXEH3Y4BmUm8nQCpfyx24tK+Y9dkCZjgfpWbJopP GtTAazwA98S+90+6Bs0ly/Q8WbP1rTzCSR0yWsrP5OrOZ3yz5dicm5tSBqTpXRFktdIL qZhxF0JzZ8Prc7AqRlyorb6KOGDZK+J8yAxL0VnKgt8cctEprEx220QXiFA76XycRqcf mtJUt49/eL4m/XVyt13Uhuoi/MesVgJaCcu5SgRLcX4CvOerTj6IRb/PExqnlVdbBpeK B3gOamQdqB2+MEpmIJoURDFTs7ftNC4uzdo8NJP+bSoJgOMRpKDmA6+MYE+79SQKWLw4 RMuw== MIME-Version: 1.0 X-Received: by 10.14.179.5 with SMTP id g5mr62110111eem.41.1365528523907; Tue, 09 Apr 2013 10:28:43 -0700 (PDT) Received: by 10.14.138.73 with HTTP; Tue, 9 Apr 2013 10:28:43 -0700 (PDT) In-Reply-To: <1365527499.4106.2.camel@localhost> References: <51622F44.3050604@FreeBSD.org> <1365441764.4112.1.camel@localhost> <51641315.3080704@bluerosetech.com> <1365526115.3607.6.camel@localhost> <1365527499.4106.2.camel@localhost> Date: Tue, 9 Apr 2013 13:28:43 -0400 Message-ID: Subject: Re: Growing list of required(ish) ports From: Robert Simmons To: florent+FreeBSD-ports@peterschmitt.fr Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Mailing List X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list 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:28:45 -0000 On Tue, Apr 9, 2013 at 1:11 PM, Florent Peterschmitt wrote: > Le mardi 09 avril 2013 =E0 13:03 -0400, Robert Simmons a =E9crit : >> > Hum, I didn't thought about that. So I think it would be possible to >> > have a secondary =AB branch =BB for the distribution including somethi= ng >> > like =AB special ports =BB which can be retrieved, built and managed (= for >> > porters) quickly. >> > >> > Anybody think something like that is relevant and possible to do ? >> >> 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. No, stable is just another type of development branch. It is not meant for production use. I'm suggesting that enough testing and QA be applied to certain updates to be able to offer them as part of freebsd-update. Not sure if this is even possible. It may go against the philosophy of RELEASE and it would require resources that are in short supply as is.