Date: Thu, 6 Mar 2008 10:52:52 +0100 From: Marco Walraven <m.walraven@terantula.com> To: freebsd-hackers@freebsd.org Subject: make index during make release generates wrong INDEX file Message-ID: <20080306095252.GP19542@cotton.terantula.com>
next in thread | raw e-mail | index | archive | help
Hi, I ran into a wrongly named INDEX file today after I did a 'make release' of RELENG_7 on a RELENG_6 system which includes the Ports Collection. The index file is named INDEX-6 instead of INDEX-7. A quick look in Mk/bsd.port.subdir.mk shows me that it will read the version from the param.h file found in either /usr/include/sys/ or /usr/src/sys/sys/ and will name the INDEX- file according to what it found. The first location holds the file from of my running system RELENG_6 (outcome of the make buildworld on which make release depends); the second location holds the RELENG_7 file, checked out during 'make release'. Shouldn't it check the param.h file that is in my chrooted environment and use the version it finds in there while doing a make release instead of the param.h from the make buildworld outcome ? Ofcourse this works fine if you are running, let's say RELENG_6 and you want to make a release for that branch as well cause then they are equal(ly). Quickfix would be to specify OSVERSION in the make.conf; however if there is already a chrooted env why should you have to specify OSVERSION since it can get the exact version from the param.h file in the chrooted env ? Thanks, Marco -- Terantula - Industrial Strength Open Source phone:+31 64 3232 400 / www: http://www.terantula.com / pgpkey: E7EE7A46 pgp fingerprint: F2EE 122D 964C DE68 7380 6F95 3710 7719 E7EE 7A46
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080306095252.GP19542>