From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: gentoo ebuild for compat wireless (resend)
Date: Tue, 25 Mar 2008 12:14:53 +0100 [thread overview]
Message-ID: <47E8DEAD.1040808@gmx.de> (raw)
In-Reply-To: <47E83DF5.9030401@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
Florian Manschwetus schrieb:
> Luis R. Rodriguez schrieb:
>> On Mon, Mar 24, 2008 at 7:31 PM, Florian Manschwetus
>> <florianmanschwetus@gmx.de> wrote:
>>> Luis R. Rodriguez schrieb:
>>>
>>>
>>>> On Mon, Mar 24, 2008 at 9:12 AM, Florian Manschwetus
>>> > <florianmanschwetus@gmx.de> 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 majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3673 bytes --]
next prev parent reply other threads:[~2008-03-25 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 13:12 gentoo ebuild for compat wireless (resend) Florian Manschwetus
2008-03-24 20:04 ` Luis R. Rodriguez
2008-03-24 23:31 ` Florian Manschwetus
2008-03-24 23:30 ` Luis R. Rodriguez
2008-03-24 23:49 ` Florian Manschwetus
2008-03-25 11:14 ` Florian Manschwetus [this message]
2008-03-25 14:25 ` Luis R. Rodriguez
2008-03-25 15:26 ` Florian Manschwetus
2008-03-25 15:29 ` Johannes Berg
2008-03-25 15:40 ` Luis R. Rodriguez
2008-03-25 17:03 ` Luis R. Rodriguez
2008-03-25 20:22 ` Luis R. Rodriguez
2008-03-25 21:42 ` Florian Manschwetus
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 18:38 sebastiaan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E8DEAD.1040808@gmx.de \
--to=florianmanschwetus@gmx.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).