gentoo ebuild for compat wireless (resend)
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
Quoted 2 lines · Florian Manschwetus
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
Quoted 14 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76
Quoted 7 lines
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-describeDoes 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
Quoted 3 lines
Luis
Quoted 23 lines · Florian Manschwetus
Quoted 20 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76You 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
Quoted 6 lines
Quoted 1 line
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
Quoted 32 lines · Luis R. Rodriguez
Quoted 23 lines · Florian Manschwetus
Quoted 20 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76You 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-describeQuoted 6 lines
Quoted 1 line
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
Quoted 5 lines
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
Quoted 7 lines
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
Quoted 39 lines · Florian Manschwetus
Quoted 38 lines · Luis R. Rodriguez
Quoted 35 lines · Florian Manschwetus
Quoted 6 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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
Quoted 12 lines
and Linux. I keep both version already as part of the tarball.
wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release 2.8-49-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76You 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
Quoted 1 line
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
Quoted 2 lines
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
Quoted 7 lines
Quoted 5 lines
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
Quoted 8 lines
Quoted 7 lines
Luis
Signature · 3 lines
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
Quoted 48 lines · Florian Manschwetus
Quoted 45 lines · Florian Manschwetus
Quoted 44 lines · Luis R. Rodriguez
Quoted 28 lines · Florian Manschwetus
Quoted 6 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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
Quoted 12 lines
and Linux. I keep both version already as part of the tarball.
wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release 2.8-49-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76You 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
Quoted 1 line
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
Quoted 1 line
Quoted 8 lines
Quoted 1 line
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.bz2The 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?
Quoted 5 lines
Quoted 2 lines
a date would be perfect (f.e. -20080325)
florianOk, 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
Quoted 56 lines · Luis R. Rodriguez
Quoted 48 lines · Florian Manschwetus
Quoted 45 lines · Florian Manschwetus
Quoted 44 lines · Luis R. Rodriguez
Quoted 28 lines · Florian Manschwetus
Quoted 6 lines · Luis R. Rodriguez
Quoted 2 lines · Florian Manschwetus
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
Quoted 12 lines
and Linux. I keep both version already as part of the tarball.
wireless@sipsolutions:~$ cat compat-wireless-2.6/compat-release 2.8-49-gfe0f268wireless@sipsolutions:~$ cat compat-wireless-2.6/git-describe v2.6.25-rc5-2623-g7556b76You 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
Quoted 1 line
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6/git-describe
Quoted 1 line
Quoted 8 lines
Quoted 1 line
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.bz2The 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?
Quoted 5 lines
Quoted 2 lines
a date would be perfect (f.e. -20080325)
florianOk, 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.
Quoted 3 lines
Does this work for you?
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2008-03-25.tar.bz2
Yes,
Quoted 3 lines
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
Quoted 7 lines
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
Quoted 7 lines
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
Quoted 6 lines · Johannes Berg
Quoted 6 lines
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)
Quoted 8 lines
Quoted 1 line
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
Quoted 18 lines · Luis R. Rodriguez
Quoted 6 lines · Johannes Berg
Quoted 6 lines
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)Quoted 8 lines
Quoted 1 line
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.
Quoted 10 lines
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
Quoted 10 lines · Luis R. Rodriguez
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
Quoted 11 lines · Luis R. Rodriguez
Quoted 9 lines · Luis R. Rodriguez
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.
Quoted 7 lines
Quoted 1 line
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
Quoted 7 lines
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