| 1 |
Hi Chris |
| 2 |
|
| 3 |
On Wednesday 31 July 2002 13:59, Christopher Sharp wrote: |
| 4 |
> Hello, |
| 5 |
> I want to make an ebuild of madplay but as libmad and madplay are in one |
| 6 |
> package I don't know how to deal with that. Should I make two ebuilds or |
| 7 |
> only one which installs both ? |
| 8 |
That depends. |
| 9 |
Is libmad a very specific library designed to run solely with madplay and |
| 10 |
nothing else? |
| 11 |
Or rather can it be used by some other app? |
| 12 |
Generally if there is a chance that it may be used by other apps it should be |
| 13 |
a separate package/ebuild (just use the same SRC_URI, anyway it will be |
| 14 |
fetched only once). Otherwise it is better to install it in the same ebuild |
| 15 |
as the sole app making use of it. |
| 16 |
|
| 17 |
If you are not sure I think in your case it is a sufficiently safe bet to |
| 18 |
assume that the lib is quite specific and just creat one ebuild that will |
| 19 |
install both the lib and the app. If later-on you find some other app making |
| 20 |
use of this lib you can just split the ebuild. And yea, definitely make a |
| 21 |
note in the ChangeLog and probably the ebuild itself, that the lib is |
| 22 |
installed along the app. This way whoever comes by this issue will be able to |
| 23 |
easily handle it. |
| 24 |
|
| 25 |
George |
Archives