From owner-freebsd-stable Fri Nov 10 0:49: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id DC04337B479; Fri, 10 Nov 2000 00:49:03 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAA8n0I22873; Fri, 10 Nov 2000 00:49:00 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Cc: nik@freebsd.org, stable@freebsd.org Subject: Re: OK, I figured out why docs aren't building in the release candidates In-Reply-To: Message from asami@freebsd.org (Satoshi - Ports Wraith - Asami) of "09 Nov 2000 15:43:24 PST." Date: Fri, 10 Nov 2000 00:49:00 -0800 Message-ID: <22869.973846140@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That is not good. We should fix it. Something like doc building > ports are *not* supposed to be broken in ports-current (which also > doubles as ports-stable). No, I meant general aspects of the ports collection were broken enough to stop the "make readmes" from working, not that the doc ports specifically were broken. That's why I can't use -current ports. > Um, you are not supposed to set it to the release tag until all parts > of the trees are tagged. ;-) I'm not - it's auto-setting itself and getting it wrong, see below. > Yes, separating it into two (both defaulting to the same value, of > course) is a good idea and will make the tags even more useful. Do > you have a patch for this, or do you want me to cook up one? Well, it's just a few lines.. I'm happy either way. :) > Actually, looking at release/Makefile, I don't see how you can > manually set AUXRELEASETAG since it's !='d from the value of You need to have it set conditionally, a local mod, though "it" would be DOCRELEASETAG and PORTSRELEASETAG in our brave-new-world scenario. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message