1 |
I am trying to package a commercial vendor's SDK as a ebuild, just |
2 |
for the sake of having everything I use in portage. No, the problem is |
3 |
that this particular vendor doesn't follow the standard OSS versioning |
4 |
scheme. The tarball I download has a name like: |
5 |
|
6 |
sdknamewithversion.architecture.tar.gz |
7 |
|
8 |
In other words: |
9 |
|
10 |
vedorsdk2.linux24.tar.gz |
11 |
|
12 |
And ofcourse they also fail to put a proper directory structure below |
13 |
that.. but that one I belive I can work around.. |
14 |
|
15 |
But how would I write a ebuild that works with that? Or do I have to |
16 |
resolve to storing it locally and rename the tarball? |
17 |
|
18 |
Best regards |
19 |
Michael Boman |
20 |
|
21 |
-- |
22 |
Michael Boman |
23 |
Security Architect, SecureCiRT Pte Ltd |
24 |
http://www.securecirt.com |