Also, forgot to mention on small detail... if you're using this approach, after checking out all the feeds, you will need to manually run:
./scripts/feeds update -a -i ./scripts/feeds install -a Don't forget to add the -i in the update. This way, the feeds on your computer will be left in its current state and indices are created, etc. Otherwise, it will try updating from git/svn. Regards, Chirag Chhatriwala On Sat, Jun 21, 2014 at 3:59 PM, Chirag Chhatriwala <[email protected]> wrote: > I generally try to do the following: > > 1. perform a git clone on the branch or trunk. > 2. perform "git log --grep="<svn_id>", grab the hashtag or commit id and > note the date and time of that checkin and perform a "git checkout <commit > id>", this will create a detached HEAD and will leave you at the <commit > it> and nothing after it. > 3. if you are going to add feeds, you need to do something similar for the > feeds as well.. I.E. create a folder named "feeds" under your source and > checkout your feeds (most likely git based now). > 4. for each feeds you checked out, perform a "git log > --before="YYYY-MM-DDThh:mm:ss+Zone" format > 5. grab the latest commit id and perform a "git checkout <feed commit id>" > (for each feed checked out) > > This way you know that everything you are building is roughly the same age > as the latest svn commit that you're trying to replicate. You may end up > missing a commit or two but you will be fairly close to building the > version you want. Its not exact science but it is close enough. Otherwise > you may end up checking out an old version of openwrt, but have it built > against the latest pacakges/luci/routing/telephony feeds and things may > (most likely will) break. > > It used to be easier when everything was svn based and you could just > specify the svn id in your feeds in the format svn://feed.location@<svn_ID>. > Things change so we adapt. > > Hope this helps. Let me know if this is not clear. > > > Chirag > > > > On Sat, Jun 21, 2014 at 8:54 AM, Nikolai Zhubr <[email protected]> > wrote: > >> 21.06.2014 14:39, Rafał Miłecki: >> >> What about using tag in svn repo? >>> svn://svn.openwrt.org/openwrt/tags/attitude_adjustment_12.09/ >>> >> >> I tried that, and although version.mk indeed stated 12.09, there is some >> discrepancy: >> >> - svn told me that it fetched r41293 this time; >> - the router flashed with this self-built 12.09 claimed it is r36422; >> - binary AA 12.09 from downloads.openwrt.org claims it is r36088. >> >> So I'm now closer, but still can't produce a build which would identify >> itself exactly as the official 12.09 release (12.09 r36088). >> >> Thank you, >> Nikolai >> >> >> >>> . >>> >>> _______________________________________________ >> openwrt-devel mailing list >> [email protected] >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
