Re: building a release
On Sat, Feb 26, 2000 at 11:47:33AM -0800, Brian Beattie wrote: > I have looked at the FAQ and find only a partial answer. I would like to > build a a release with base and X11, to do local installs of > 4.0-current. I can build the base from /usr/src/release, I have the > XFree86 sources. > > Can anybody send me notes, or point me at the FAQ? I have tried the same thing last week. All I can say is that you definitely need to run the same -current to build a release of the tree. So, do an installworld first and reboot (or fetch a -current release of the net for now, such as I did) and then go into src/release and follow the instructions in the Makefile. Something like make release CHROOTDIR=/some/dir is required. The CHROOT is the problem with older releases. If you don't run the same kernel, your libc and make etc wil run into problems. I haven't taken this to success, maybe others can add. Joerg -- Joerg B. MicheelEmail: <[EMAIL PROTECTED]> Waikato Applied Network DynamicsPhone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Building a release
> Why? I'm wondering if this is the problem as both ports and > doc are not populated. > > Any suggestions, ideas? The ports and doc collections use tags of the form RELEASE_X_Y_Z, while src uses RELENG_X_Y_Z_RELEASE. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a release
At about the time of 12/27/2005 6:07 AM, Joseph Koshy stated the following: >>Why? I'm wondering if this is the problem as both ports and >>doc are not populated. >> >>Any suggestions, ideas? > > > The ports and doc collections use tags of the form RELEASE_X_Y_Z, > while src uses RELENG_X_Y_Z_RELEASE. > I'll try that then. Thanks. -- Daniel Rudy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a release
At about the time of 12/27/2005 6:07 AM, Joseph Koshy stated the following: >>Why? I'm wondering if this is the problem as both ports and >>doc are not populated. >> >>Any suggestions, ideas? > > > The ports and doc collections use tags of the form RELEASE_X_Y_Z, > while src uses RELENG_X_Y_Z_RELEASE. > > -- > FreeBSD Volunteer, http://people.freebsd.org/~jkoshy > Didn't work, same problem. -- Daniel Rudy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a release
If memory serves me right, Daniel Rudy wrote: > I'm having some difficulties in building a release ISO from sources. > When I do a make release in /usr/src/release, everything seems to go > well until is tries to access perl5.8 in the ports. I go into ports and > find that there is nothing there. Here's what I have been doing: > > Build directory trees: > mkdir /usr/cvsroot > mkdir /usr/release > mkdir /usr/tmp/cvs > > Get CVS tree: > cd /usr/tmp/cvs > cvs -d [EMAIL PROTECTED]:/home/ncvs co -rRELENG_6_0_0_RELEASE src > cvs -d [EMAIL PROTECTED]:/home/ncvs co doc > cvs -d [EMAIL PROTECTED]:/home/ncvs co ports > > Build local CVS repository: > cd /usr/cvsroot > CVSROOT=/usr/cvsroot ; export CVSROOT > CVSEDITOR=vi ; export CVSEDITOR > cvs init > cd /usr/tmp/cvs/src > cvs import src RELENG_6_0_0_RELEASE src > cd /usr/tmp/cvs/doc > cvs import doc RELENG_6_0_0_RELEASE doc > cd /usr/tmp/cvs/ports > cvs import ports RELENG_6_0_0_RELEASE ports Any particular reason that you're trying to recreate FreeBSD's CVS repository layout, rather than just grabbing a copy of the repository? I haven't thought much about this problem but it seems to me you're winding up with tags in your reconstructed repository that are not the same as the tags in the "real" repository, and this may be causing some problems. I could picture you wanting to do this if you were tragically low on disk space but until you get some success at actually building a release, you might be better off stucking to a more "normal" setup. Good luck! Bruce. signature.asc Description: OpenPGP digital signature
Re: Building a release
Better to just use cvsup /usr/share/examples/cvsup/cvs-supfile then all u need to do is create /home/cvs first. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
