| 1 |
On Tue, Aug 10, 2010 at 10:22 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Tue, 10 Aug 2010 18:53:12 +0200, Alex Schuster wrote: |
| 3 |
> |
| 4 |
>> ebuild /path/to/category/package.ebuild unpack |
| 5 |
>> |
| 6 |
>> Read the man page, I'm not sure if things like fetching will be done |
| 7 |
>> when necessary. |
| 8 |
> |
| 9 |
> It will, ebuild carries out any prior steps if they are needed. You may |
| 10 |
> want to use ebuild ... prepare instead of ebuild ... unpack. It carries |
| 11 |
> out any pre-compilation steps, like applying patches. |
| 12 |
> |
| 13 |
> If you are doing this because you want to apply a patch yourself, you can |
| 14 |
> use one of the above, apply your patches, then run ebuild ... merge to |
| 15 |
> complete the process and install it. man 1 ebuild explains it all. |
| 16 |
> |
| 17 |
> |
| 18 |
> -- |
| 19 |
> Neil Bothwick |
| 20 |
> |
| 21 |
> What do you do when you see an endangered animal eating an endangered |
| 22 |
> plant? |
| 23 |
> |
| 24 |
|
| 25 |
In my case, due to conversations on another list about a piece of |
| 26 |
software that's important to me, it was simply to look at how |
| 27 |
copyrights are set up in that program's source code. (I.e. - who's |
| 28 |
names are named, what dates, etc.) |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Mark |
Archives