From owner-freebsd-questions@FreeBSD.ORG Thu Jun 12 06:21:36 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96BCA37B401 for ; Thu, 12 Jun 2003 06:21:36 -0700 (PDT) Received: from hotmail.com (law9-oe34.law9.hotmail.com [64.4.8.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B37543FA3 for ; Thu, 12 Jun 2003 06:21:36 -0700 (PDT) (envelope-from ccorayer@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 12 Jun 2003 06:21:35 -0700 Received: from 66.30.133.209 by law9-oe34.law9.hotmail.com with DAV; Thu, 12 Jun 2003 13:21:35 +0000 X-Originating-IP: [66.30.133.209] X-Originating-Email: [ccorayer@hotmail.com] From: "chris corayer" Cc: References: <20030612042523.59748.qmail@mx.tele-kom.ru> Date: Thu, 12 Jun 2003 09:29:15 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: X-OriginalArrivalTime: 12 Jun 2003 13:21:35.0898 (UTC) FILETIME=[8C7A5FA0:01C330E5] Subject: Re: Are there STABLE/CURRENT/RELEASE tags for ports? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2003 13:21:37 -0000 You could try specifying a date in your cvsupfile. This isn't exactly what you are looking for but if you tried to update a port and find it no longer works, you could then roll back the changes made with another cvsup for the ports. I have done this in the past but don't recall the exact syntax. Try man cvsup. I would consider setting up another cvsup file for just this purpose if you think it will happen often. You could set the date to when the new version came out, sort of a "release" date, or just increment it until you get it to the point where you know it builds and go from there. Hope this helps a little. -Chris ----- Original Message ----- From: "DoubleF" To: "Mark Miller" Cc: Sent: Thursday, 12 June, 2003 0:23 Subject: Re: Are there STABLE/CURRENT/RELEASE tags for ports? > > Are there any equivalents to STABLE/RELEASE/CURRENT for ports? I've been > > cvsup'ing with "tag=." for awhile and I keep getting build errors (bug > > reports will be filed soon). Is there a way to just track -STABLE ports > > (maybe that only have bugfixes and security updates) that are more likely > > to play nicely with each other? If not, is there any way to make this > > happen? > > Arghh I wish there were such tags. > > In the meantime you might consider CTM for ports, downloading the deltas > from the FTP. If you do that and NEVER EVER remove the deltas, you may > be able to 'roll back' to any date you want to try to find the non-broken > port version (if there was any, of course...). > > I am also rather tired of build errors. What I can suggest is probably > kludgy, but it is the least kludgy way I could find to compile some > ports. Before you install any ports, > > 1) Save the deltas... > > > 2) Symlink /usr/X11R6 to /usr/local. Many ports put files in the wrong > one, and symlinking individual files is, ahm,... AFAIK, there are no > colliding files in them. > > 3) Try putting /usr/local and /var/db/pkg (and /etc/X11, and /usr/ports > maybe, but I don't) on a separate filesystem. Make two such filesystems, > "current" and "stable". Make / and the remaining /usr as read-only as > possible. Make a mountpoint, say, /switch. Symlink /usr/local to > /switch/usr.local, /var/db/pkg to /switch/var.db.pkg... Then change the > fstab file to mount "stable" at startup. You can always mount "current" > after boot on top of "stable" and so emulate what you wish. You may want > to make the WRKDIRPREFIX to point to a directory shared between the > "current" and "stable" to save compilation time (otherwise you will > compile each port twice), but I wouldn't recommend it (to be on the safe > side). > > > It's just what I do. I know it breaks the normal hierarchy (and takes 2x > space), but at least it does it in a polite way. > > HTH, > DoubleF > > >