| 1 |
On Mon, 2003-03-03 at 20:20, Michael Boman wrote: |
| 2 |
> I am trying to package a commercial vendor's SDK as a ebuild, just |
| 3 |
> for the sake of having everything I use in portage. No, the problem is |
| 4 |
> that this particular vendor doesn't follow the standard OSS versioning |
| 5 |
> scheme. The tarball I download has a name like: |
| 6 |
> |
| 7 |
> sdknamewithversion.architecture.tar.gz |
| 8 |
> |
| 9 |
> In other words: |
| 10 |
> |
| 11 |
> vedorsdk2.linux24.tar.gz |
| 12 |
> |
| 13 |
> And ofcourse they also fail to put a proper directory structure below |
| 14 |
> that.. but that one I belive I can work around.. |
| 15 |
> |
| 16 |
> But how would I write a ebuild that works with that? Or do I have to |
| 17 |
> resolve to storing it locally and rename the tarball? |
| 18 |
> |
| 19 |
|
| 20 |
Name the ebuild: |
| 21 |
foopackage-version.ebuild |
| 22 |
|
| 23 |
Munge the SRC_URI like so: |
| 24 |
|
| 25 |
SRC_URI="http:/stupidvendor/foopackage-${PV}-linux24.tar.gz" |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Troy Dack http://linux.tkdack.com |
| 30 |
<troy@××××××.com> http://webportage.sf.net |
| 31 |
|
| 32 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C |
| 33 |
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96 92E5 FD89 16F9 4D90 BE3C |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives