> 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
Descr
On 04/03/11 12:42, Imre Kaloz wrote:
> On Fri, 04 Mar 2011 11:05:02 +0100, Mark Vels
> wrote:
>
>
>>> in my opinion is that the developers community of OpenWRT has no
>>> interest in keeping a tagged packages tree.
>
> Right
Did you forget the tags here?
>
>> Please add at least a revision numbe
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 anythin
On Fri, 04 Mar 2011 11:05:02 +0100, Mark Vels
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!
Sure, and y
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 i
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 tagg
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 t
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 hav
-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.defa
> 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.
Saverio
_
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
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.
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 wrote:
> Hello,
>
> I am
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
14 matches
Mail list logo
