is it possible to get a version appendix on the tar.bz?
so it should be easy to get a working ebuild fpr this.
florian
this is a resend of the message, caused if subscribtion problems
> but this is a problem, when i distribute a ebuild it is useful to have a
> locked version, so that i get reproducible results.
> My problem, is that i have currently no resources to rehost this
> tar-ball. (no official gentoo-dev, no reliable webserver)
>
> But, i see currently no other solution than rehosting.
We can keep a few around, but definitely not forever, so you'll have to
find somewhere else to host your "known good" versions. While I could do
it resource-wise, I don't want the admin overhead of having various
distros tell us which ones are known-good for them.
You could simply get a gentoo dev to help you out.
Thanks,
johannes
On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
<[email protected]> wrote:
> is it possible to get a version appendix on the tar.bz?
> so it should be easy to get a working ebuild fpr this.
The problem is there's two things to "version", compat-wireless itself
and Linux. I keep both version already as part of the tarball.
wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
2.8-49-gfe0f268
wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
v2.6.25-rc5-2623-g7556b76
You can also just pull these from the directory that was used to
create the tarball:
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
Does this suffice?
Luis
On Tue, Mar 25, 2008 at 1:03 PM, Luis R. Rodriguez <[email protected]> wrote:
> OK so now you have:
>
>
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
>
> You can wget this. The compat-wireless-2.6.tar.bz2 is now just a
> symlink to the latest tarball. When untar'd you'll get a dated
> directory.
>
> I'm still working on a place to put the archive.
Archive issue resolved. It'll be hosted by Orbit [1]. The
compat-wireless-2.6 archive [2] will host all daily tarballs.
[1] http://www.orbit-lab.org/
[2] http://www.orbit-lab.org/kernel/compat-wireless-2.6/
Luis
On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
<[email protected]> wrote:
> Luis R. Rodriguez schrieb:
>
>
> > On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
> > <[email protected]> wrote:
> >> is it possible to get a version appendix on the tar.bz?
> >> so it should be easy to get a working ebuild fpr this.
> >
> > The problem is there's two things to "version", compat-wireless itself
> > and Linux. I keep both version already as part of the tarball.
> >
> > wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
> > 2.8-49-gfe0f268
> >
> > wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
> > v2.6.25-rc5-2623-g7556b76
> >
> > You can also just pull these from the directory that was used to
> > create the tarball:
> >
> > http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
> > http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
> >
> > Does this suffice?
>
>
> Not really but it gives a version hint, could you create a symlink or so?
> a url like that would be fine:
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
The problem is that does not reflect changes to Linux so there may be
a lot of great code added and yet this wouldn't reflect it. And if we
go with git-describe for Linux we could get updates on compat-wireless
itself during no code changes on Linux. I could use date (date -I),
that might work best but will it work for you?
Luis
Luis R. Rodriguez schrieb:
> On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
> <[email protected]> wrote:
>> Luis R. Rodriguez schrieb:
>>
>>
>>> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
>> > <[email protected]> wrote:
>> >> is it possible to get a version appendix on the tar.bz?
>> >> so it should be easy to get a working ebuild fpr this.
>> >
>> > The problem is there's two things to "version", compat-wireless itself
>> > and Linux. I keep both version already as part of the tarball.
>> >
>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
>> > 2.8-49-gfe0f268
>> >
>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
>> > v2.6.25-rc5-2623-g7556b76
>> >
>> > You can also just pull these from the directory that was used to
>> > create the tarball:
>> >
>> > http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
>> > http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
>> >
>> > Does this suffice?
>>
>>
>> Not really but it gives a version hint, could you create a symlink or so?
>> a url like that would be fine:
>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
>
> The problem is that does not reflect changes to Linux so there may be
> a lot of great code added and yet this wouldn't reflect it. And if we
> go with git-describe for Linux we could get updates on compat-wireless
> itself during no code changes on Linux. I could use date (date -I),
> that might work best but will it work for you?
a date would be perfect (f.e. -20080325)
florian
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Tue, Mar 25, 2008 at 11:40 AM, Luis R. Rodriguez <[email protected]> wrote:
>
> On Tue, Mar 25, 2008 at 11:29 AM, Johannes Berg
> <[email protected]> wrote:
> >
> > > but this is a problem, when i distribute a ebuild it is useful to have a
> > > locked version, so that i get reproducible results.
> > > My problem, is that i have currently no resources to rehost this
> > > tar-ball. (no official gentoo-dev, no reliable webserver)
> > >
> > > But, i see currently no other solution than rehosting.
> >
> > We can keep a few around, but definitely not forever, so you'll have to
> > find somewhere else to host your "known good" versions. While I could do
> > it resource-wise, I don't want the admin overhead of having various
> > distros tell us which ones are known-good for them.
> >
> > You could simply get a gentoo dev to help you out.
>
> I can probably get a historic archive of the tarballs hosted on orbit
> or winlab site. Give me a few and I'll start something. Let me remind
> you now that compat-wireless-2.6.tar.bz2 tarball has anti-hotlinking
> enabled but the compat-wireless-2008-* tarballs won't. Anti-hotlinking
> disables people from linking to the tarball externally, this will
> force them to read the Download page if redirected from a separate
> page, once they go there they can download the tarball. The dated
> tarballs don't have this anti-hotlinking enabled now (Johannes just
> set this up) so the ebuild/wget'ing should work directly for the dated
> tarballs.
OK so now you have:
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
You can wget this. The compat-wireless-2.6.tar.bz2 is now just a
symlink to the latest tarball. When untar'd you'll get a dated
directory.
I'm still working on a place to put the archive.
Luis
On Tue, Mar 25, 2008 at 7:14 AM, Florian Manschwetus
<[email protected]> wrote:
> Florian Manschwetus schrieb:
>
>
> > Luis R. Rodriguez schrieb:
> >> On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
> >> <[email protected]> wrote:
> >>> Luis R. Rodriguez schrieb:
> >>>
> >>>
> >>>> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
> >>> > <[email protected]> wrote:
> >>> >> is it possible to get a version appendix on the tar.bz?
> >>> >> so it should be easy to get a working ebuild fpr this.
> >>> >
> >>> > The problem is there's two things to "version", compat-wireless
> >>> itself
> >>> > and Linux. I keep both version already as part of the tarball.
> >>> >
> >>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
> >>> > 2.8-49-gfe0f268
> >>> >
> >>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
> >>> > v2.6.25-rc5-2623-g7556b76
> >>> >
> >>> > You can also just pull these from the directory that was used to
> >>> > create the tarball:
> >>> >
> >>> >
> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
> >>>
> >>> >
> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
> >>>
> >>> >
> >>> > Does this suffice?
> >>>
> >>>
> >>> Not really but it gives a version hint, could you create a symlink or
> >>> so?
> >>> a url like that would be fine:
> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
> >>>
> >>
> >> The problem is that does not reflect changes to Linux so there may be
> >> a lot of great code added and yet this wouldn't reflect it. And if we
> >> go with git-describe for Linux we could get updates on compat-wireless
> >> itself during no code changes on Linux. I could use date (date -I),
> >> that might work best but will it work for you?
> > a date would be perfect (f.e. -20080325)
> > florian
> Ok, i got a working ebuild, no i need an regular accessible download
> source with "solid" filenames e.g. the date appendix, then i could
> publish it as testing package.
Does this work for you?
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
Note that I'll delete all old tarballs when generating a new one for
the new date. This happens at 05:10am UTC.
Luis
Luis R. Rodriguez schrieb:
> On Tue, Mar 25, 2008 at 7:14 AM, Florian Manschwetus
> <[email protected]> wrote:
>> Florian Manschwetus schrieb:
>>
>>
>>> Luis R. Rodriguez schrieb:
>> >> On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
>> >> <[email protected]> wrote:
>> >>> Luis R. Rodriguez schrieb:
>> >>>
>> >>>
>> >>>> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
>> >>> > <[email protected]> wrote:
>> >>> >> is it possible to get a version appendix on the tar.bz?
>> >>> >> so it should be easy to get a working ebuild fpr this.
>> >>> >
>> >>> > The problem is there's two things to "version", compat-wireless
>> >>> itself
>> >>> > and Linux. I keep both version already as part of the tarball.
>> >>> >
>> >>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
>> >>> > 2.8-49-gfe0f268
>> >>> >
>> >>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
>> >>> > v2.6.25-rc5-2623-g7556b76
>> >>> >
>> >>> > You can also just pull these from the directory that was used to
>> >>> > create the tarball:
>> >>> >
>> >>> >
>> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
>> >>>
>> >>> >
>> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
>> >>>
>> >>> >
>> >>> > Does this suffice?
>> >>>
>> >>>
>> >>> Not really but it gives a version hint, could you create a symlink or
>> >>> so?
>> >>> a url like that would be fine:
>> >>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
>> >>>
>> >>
>> >> The problem is that does not reflect changes to Linux so there may be
>> >> a lot of great code added and yet this wouldn't reflect it. And if we
>> >> go with git-describe for Linux we could get updates on compat-wireless
>> >> itself during no code changes on Linux. I could use date (date -I),
>> >> that might work best but will it work for you?
>> > a date would be perfect (f.e. -20080325)
>> > florian
>> Ok, i got a working ebuild, no i need an regular accessible download
>> source with "solid" filenames e.g. the date appendix, then i could
>> publish it as testing package.
>
> Does this work for you?
>
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
Yes,
>
> Note that I'll delete all old tarballs when generating a new one for
> the new date. This happens at 05:10am UTC.
but this is a problem, when i distribute a ebuild it is useful to have a
locked version, so that i get reproducible results.
My problem, is that i have currently no resources to rehost this
tar-ball. (no official gentoo-dev, no reliable webserver)
But, i see currently no other solution than rehosting.
Normally gentoo uses official upstream src locations, and mirrors all
stuff present in portage to reduce load on official websites.
(portage first looks on gentoo-mirrors for tar-ball if unavailable it
loads from official download page).
florian
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Luis R. Rodriguez schrieb:
> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
> <[email protected]> wrote:
>> is it possible to get a version appendix on the tar.bz?
>> so it should be easy to get a working ebuild fpr this.
>
> The problem is there's two things to "version", compat-wireless itself
> and Linux. I keep both version already as part of the tarball.
>
> wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
> 2.8-49-gfe0f268
>
> wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
> v2.6.25-rc5-2623-g7556b76
>
> You can also just pull these from the directory that was used to
> create the tarball:
>
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
>
> Does this suffice?
Not really but it gives a version hint, could you create a symlink or so?
a url like that would be fine:
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
florian
>
> Luis
>
Florian Manschwetus schrieb:
> Luis R. Rodriguez schrieb:
>> On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
>> <[email protected]> wrote:
>>> Luis R. Rodriguez schrieb:
>>>
>>>
>>>> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
>>> > <[email protected]> wrote:
>>> >> is it possible to get a version appendix on the tar.bz?
>>> >> so it should be easy to get a working ebuild fpr this.
>>> >
>>> > The problem is there's two things to "version", compat-wireless
>>> itself
>>> > and Linux. I keep both version already as part of the tarball.
>>> >
>>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release
>>> > 2.8-49-gfe0f268
>>> >
>>> > wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe
>>> > v2.6.25-rc5-2623-g7556b76
>>> >
>>> > You can also just pull these from the directory that was used to
>>> > create the tarball:
>>> >
>>> >
>>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/compat-release
>>>
>>> >
>>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
>>>
>>> >
>>> > Does this suffice?
>>>
>>>
>>> Not really but it gives a version hint, could you create a symlink or
>>> so?
>>> a url like that would be fine:
>>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.8-49.tar.bz2
>>>
>>
>> The problem is that does not reflect changes to Linux so there may be
>> a lot of great code added and yet this wouldn't reflect it. And if we
>> go with git-describe for Linux we could get updates on compat-wireless
>> itself during no code changes on Linux. I could use date (date -I),
>> that might work best but will it work for you?
> a date would be perfect (f.e. -20080325)
> florian
Ok, i got a working ebuild, no i need an regular accessible download
source with "solid" filenames e.g. the date appendix, then i could
publish it as testing package.
florian
>>
>> Luis
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
On Tue, Mar 25, 2008 at 11:29 AM, Johannes Berg
<[email protected]> wrote:
>
> > but this is a problem, when i distribute a ebuild it is useful to have a
> > locked version, so that i get reproducible results.
> > My problem, is that i have currently no resources to rehost this
> > tar-ball. (no official gentoo-dev, no reliable webserver)
> >
> > But, i see currently no other solution than rehosting.
>
> We can keep a few around, but definitely not forever, so you'll have to
> find somewhere else to host your "known good" versions. While I could do
> it resource-wise, I don't want the admin overhead of having various
> distros tell us which ones are known-good for them.
>
> You could simply get a gentoo dev to help you out.
I can probably get a historic archive of the tarballs hosted on orbit
or winlab site. Give me a few and I'll start something. Let me remind
you now that compat-wireless-2.6.tar.bz2 tarball has anti-hotlinking
enabled but the compat-wireless-2008-* tarballs won't. Anti-hotlinking
disables people from linking to the tarball externally, this will
force them to read the Download page if redirected from a separate
page, once they go there they can download the tarball. The dated
tarballs don't have this anti-hotlinking enabled now (Johannes just
set this up) so the ebuild/wget'ing should work directly for the dated
tarballs.
Luis
Luis R. Rodriguez schrieb:
> On Tue, Mar 25, 2008 at 1:03 PM, Luis R. Rodriguez <[email protected]> wrote:
>
>> OK so now you have:
>>
>>
>> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
>>
>> You can wget this. The compat-wireless-2.6.tar.bz2 is now just a
>> symlink to the latest tarball. When untar'd you'll get a dated
>> directory.
>>
>> I'm still working on a place to put the archive.
>
> Archive issue resolved. It'll be hosted by Orbit [1]. The
> compat-wireless-2.6 archive [2] will host all daily tarballs.
>
> [1] http://www.orbit-lab.org/
> [2] http://www.orbit-lab.org/kernel/compat-wireless-2.6/
Sounds good, thx.
Florian
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus wrote:
> so it should be easy to get a working ebuild fpr this.
Is this ebuild in some repository or can I download it somewhere?
thanks in advance