Hello list, I'm using cvsup to update my FreeBSD boxes trough a local cvsup mirror that I cvsup only when only when I want/need because I want to avoid boxes running different versions of FreeBSD/ports. What I would like to do is to update the base and the ports at differents time intervals. Working with two 'versions' will help me to update my ports more often (e.g.: security issues) while the base will be updated less often depending more on my own requirements (except for security and critical fixes). cvsup-mirror (package used on my mirror) is great but it doesn't seem to be easy / clean to implement what I want with it. Am I missing something here ? I know that I can cvsup (on the client) the base and ports at a different period but I want to be able to keep the same src tree across multiple ports tree updates (on my mirror). Running a jail is a possibility but I'm first looking for other users experiences... Regards, Benjamin Constant TI Automotive The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive.
On Tue, 22 Mar 2005, Constant, Benjamin wrote:> I'm using cvsup to update my FreeBSD boxes trough a local cvsup mirror that > I cvsup only when only when I want/need because I want to avoid boxes > running different versions of FreeBSD/ports. > > What I would like to do is to update the base and the ports at differents > time intervals. Working with two 'versions' will help me to update my ports > more often (e.g.: security issues) while the base will be updated less often > depending more on my own requirements (except for security and critical > fixes).I'm not sure I understand exactly what you are trying to achieve, but can you not simply use the date option in your supfile to make sure all systems run the exact same checkout? eg, adding something like date=2005.03.22.00.00.00 to your supfile on all the hosts? That way, it doesn't matter if you update your mirror, you'll still be getting the same checkout every time. Just make sure the date you specify is at least a few hours before your last checkout, otherwise you may miss some files which have been committed but which the mirrors between your client and the master sever haven't picked up yet. Gavin
> I'm not sure I understand exactly what you are trying to > achieve, but can you not simply use the date option in your > supfile to make sure all systems run the exact same checkout? > eg, adding something like date=2005.03.22.00.00.00 to your > supfile on all the hosts?I want to do keep the same base (FreeBSD stable) over multiple ports update so when I install a new server after having synch my mirror I'm sure it gets the same base (src-all) as the servers that were installed before the update of the mirror. Regarding the ports tree, I want to be able to update it quite often (first on the mirror, then on the hosts) depending on the security fixes available. One step ahead for me is to have a mirror providing only a frozen src-all tree and another one providing up to date src-all and ports trees so I can test the base before going on production.> That way, it doesn't matter if you update your mirror, you'll > still be getting the same checkout every time. Just make > sure the date you specify is at least a few hours before your > last checkout, otherwise you may miss some files which have > been committed but which the mirrors between your client and > the master sever haven't picked up yet.I think this may work if I use two cvsup files (one for the src-all and the other one for the ports) using a different date inside. Thank you! Benjamin Constant. The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive.
> On March 22, 2005 11:50 pm, Constant, Benjamin wrote: > > I think this may work if I use two cvsup files (one for the src-all > > and the other one for the ports) using a different date inside. > > You should always use separate supfiles for the source and > ports trees. > Why? Because the ports tree changes on a daily basis, and > the source tree may only change every couple of months > (depending on the branch you are tracking). Why compare > every single file in the source tree on your system and the > cvsup server when all you want to do is get the latest ports tree??I agree with you.> Keep them separate. Keep the tags separate. And only update > the source tree when you need to.This is what I want to do but I must be sure that if I update my mirror, I can use the same base across multiple updates. That's why the date parameter sounds interesting to me.> And, if all your systems are on a LAN, then why not NFS mount > the /usr/src and /usr/ports directories off a central system? > That way, you only have to update one system, and you're > guaranteed that all the servers have the same source and > ports trees. Just set the work directory prefix (it's listed > in the ports(7) man page) so that the compilation work > directories are local, and you're set.Unfortunately I can't but the idea is good :-)> Alternatively, just have 1 build system that makes packages, > and copy those packages out to the other servers, and do the > installs/upgrades with packages.This is also a good way of working as it help you to remove (for example) compiler stuff from your system. Keeping your installation as minimal as possible is always a good choice. Thank your for these tips. Regards, Benjamin Constant. The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive.