Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
On 03/02/2011 05:39 PM, ZioPRoTo (Saverio Proto) wrote: The source tree is tagged. LuCI is tagged. But packages apparently isn't. this thing of having packages feed tagged comes back from time to time. in my opinion is that the developers community of OpenWRT has no interest in keeping a tagged packages tree. IMHO they should! I completely agree with Daniel! One of the prime reasons for using a source control system should be to make past releases reproducible but also to make changes controllable. I think it is evil to check out a stable and tested branch like backfire and then getting different bleeding edge app versions every time you checkout a new working dir. This means that it is in practice impossible to create two working directories at different moments and have them build the same binaries, as you sometimes want to go back in time and search for regressions. Please add at least a revision number in feeds.conf for anything else than bleeding edge! Time to grow up! Daniel +1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
On Fri, 2011-03-04 at 11:05 +0100, Mark Vels wrote: Please add at least a revision number in feeds.conf for anything else than bleeding edge! Time to grow up! Yes, IMHO every OpenWRT tag and preferably every branch should contain a feeds.conf file with revision numbers set for the trees it depends on. Regards, -- Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
On Fri, 04 Mar 2011 11:05:02 +0100, Mark Vels mark.v...@team-embedded.nl wrote: in my opinion is that the developers community of OpenWRT has no interest in keeping a tagged packages tree. Right Please add at least a revision number in feeds.conf for anything else than bleeding edge! Time to grow up! sarcasm Sure, and you would have all the secholes and obsolete software as well. Sounds awesome. /sarcasm Time to grow up! Imre P.S: If you need a specific revision for bugtracking/testing, you should be smart enough to figure out how to get there. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
Hello, Imre Kaloz wrote: P.S: If you need a specific revision for bugtracking/testing, you should be smart enough to figure out how to get there. How am I supposed to figure out the exact revision number corresponding to a particular binary release (or release candidate)? Does it cost anything to tag the whole thing every time a binary release is published? For now, I have been begging knowledgeable people (you know who you are) on IRC for revision numbers, to whom I would hereby like to express my eternal gratitude, but it would be so much easier for everyone concerned to just use a tag. Cheers, -- Daniel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
How am I supposed to figure out the exact revision number corresponding to a particular binary release (or release candidate)? So far we mentioned it in every release note, posted to the devel list, the users list, the forum and for finals in the Trac roadmap again. - Jow PGP.sig Description: Signierter Teil der Nachricht ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
On 3/1/11 7:44 PM, Daniel A. Nagy wrote:
Hello,
On 03/02/2011 04:36 AM, devendra.aaru wrote:
hello,
you can do this by
touch package/your-package-name/Makefile
and compile openwrt which ensures that your-package-name compiles.
or you can delete whole build_dir and compile again which also the same.
regards,
dev.
I guess, we are having a bit of a misunderstanding here. My problem is
that the packages feed configured as
src-svn packages svn://svn.openwrt.org/openwrt/packages
is continually evolving and I am not sure how to compile some released
version of OpenWrt (say, 10.03 backfire) in such a way that the packages
from this feed are the same versions as those in the official binary
distribution.
The source tree is tagged. LuCI is tagged. But "packages" apparently isn't.
Regards,
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I had this issue as well. Here is a patch that I think does the
right thing. I am no svn expert though ... and I added src-cvs as a
source protocol as well. This patch works with a feeds.conf that
looks like:
src-cvs cortina design/sw/common/openwrt/package;GOLDEN
src-svn packages svn://svn.openwrt.org/openwrt/packages;25461
src-svn luci
http://svn.luci.subsignal.org/luci/trunk/contrib/package;6853
diff -Naur old/scripts/feeds new/scripts/feeds
--- old/scripts/feeds 2011-02-04 15:59:09.0 -0800
+++ new/scripts/feeds 2011-02-23 13:02:49.0 -0800
@@ -104,8 +104,15 @@
my %update_method = (
'src-svn' = {
'init' = "svn checkout '%s' '%s'",
+ 'init_branch' = "svn checkout -r '%s' '%s' '%s'",
'update'= "svn update",
+ 'update_branch' = "svn update -r '%s'",
'controldir'= ".svn"},
+ 'src-cvs' = {
+ 'init' = "(module='%s'; path='%s'; mkdir -p \$path; bn=`basename \$path`; cd `dirname \$path`; cvs checkout -Pd \$bn \$module)",
+ 'init_branch' = "(branch='%s'; module='%s'; path='%s'; mkdir -p \$path; bn=`basename \$path`; cd `dirname \$path`; cvs checkout -r\$branch -Pd \$bn \$module)",
+ 'update'= "cvs update -Pd",
+ 'controldir'= "CVS"},
'src-cpy' = {
'init' = "cp -Rf '%s' '%s'",
'update'= ""},
@@ -154,7 +161,11 @@
system(sprintf($m-{'init'}, $src, $safepath)) == 0 or return 1;
}
} else {
- system("cd '$safepath'; $m-{'update'}") == 0 or return 1;
+ if ($m-{'update_branch'} and $branch ) {
+ system("cd '$safepath'; " . sprintf($m-{'update_branch'}, $branch)) == 0 or return 1;
+ } else {
+ system("cd '$safepath'; $m-{'update'}") == 0 or return 1;
+ }
}
return 0;
@@ -283,6 +294,7 @@
my %install_method = (
'src-svn' = \install_generic,
+ 'src-cvs' = \install_generic,
'src-cpy' = \install_generic,
'src-link' = \install_generic,
'src-git' = \install_generic,
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.03.2011 22:47, Daniel A. Nagy wrote: Hello, I am wondering how to make sure that a re-compilation of a released (tagged) OpenWrt distribution from svn would result in compiling the same packages that come from feeds, as feeds.conf.default points to repositories that are in flux, not to tagged releases? - -src-svn packages svn://svn.openwrt.org/openwrt/packages +src-svn packages svn://svn.openwrt.org/openwrt/packages@20732 Revision taken from https://dev.openwrt.org/milestone/Backfire%2010.03 ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1udggACgkQdputYINPTPO2AQCfW/40WW6jXKik4zsbCK8zogcW aW0AoJQIIZH9Ot0JVu/82EHH4y7e3rfp =doyl -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
Jo-Philipp Wich wrote: -src-svn packages svn://svn.openwrt.org/openwrt/packages +src-svn packages svn://svn.openwrt.org/openwrt/packages@20732 Revision taken from https://dev.openwrt.org/milestone/Backfire%2010.03 Thank you so much! Would you mind tagging it? Also, it would be nice to have tags for the source of various 10.03.1 release candidate sources. Not just the packages feed, but also the actual OpenWrt source. Right now, I have no idea, from what sources the release candidates have been compiled. Thanks in advance! With kind regards, -- Daniel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
ZioPRoTo (Saverio Proto) wrote: The source tree is tagged. LuCI is tagged. But packages apparently isn't. this thing of having packages feed tagged comes back from time to time. in my opinion is that the developers community of OpenWRT has no interest in keeping a tagged packages tree. There is no extra work involved in keeping anything. Just each time a release is done an svn cp command should be run. It does not bloat the repository, subversion does this very efficiently. Regards, -- Daniel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re-compiling released OpenWrt versions
Hello, I am wondering how to make sure that a re-compilation of a released (tagged) OpenWrt distribution from svn would result in compiling the same packages that come from feeds, as feeds.conf.default points to repositories that are in flux, not to tagged releases? Thanks in advance! -- Daniel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
hello, you can do this by touch package/your-package-name/Makefile and compile openwrt which ensures that your-package-name compiles. or you can delete whole build_dir and compile again which also the same. regards, dev. On Wed, Mar 2, 2011 at 6:47 AM, Daniel A. Nagy nagyd...@epointsystem.orgwrote: Hello, I am wondering how to make sure that a re-compilation of a released (tagged) OpenWrt distribution from svn would result in compiling the same packages that come from feeds, as feeds.conf.default points to repositories that are in flux, not to tagged releases? Thanks in advance! -- Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Re-compiling released OpenWrt versions
Hello, On 03/02/2011 04:36 AM, devendra.aaru wrote: hello, you can do this by touch package/your-package-name/Makefile and compile openwrt which ensures that your-package-name compiles. or you can delete whole build_dir and compile again which also the same. regards, dev. I guess, we are having a bit of a misunderstanding here. My problem is that the packages feed configured as src-svn packages svn://svn.openwrt.org/openwrt/packages is continually evolving and I am not sure how to compile some released version of OpenWrt (say, 10.03 backfire) in such a way that the packages from this feed are the same versions as those in the official binary distribution. The source tree is tagged. LuCI is tagged. But packages apparently isn't. Regards, -- Daniel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
