| 1 |
Jesús Guerrero ha scritto: |
| 2 |
> On Mon, January 26, 2009 17:48, Mike Kazantsev wrote: |
| 3 |
>> On Mon, 26 Jan 2009 08:41:52 -0800 |
| 4 |
>> Grant <emailgrant@×××××.com> wrote: |
| 5 |
>> |
| 6 |
>>> What do you guys think of this? Do you know of a good cruft removal |
| 7 |
>>> script? |
| 8 |
>> Yep, there's quite good one in gentoo itself. |
| 9 |
>> |
| 10 |
>> Basically, you'll need to write a short config for it, consisting of |
| 11 |
>> lines like "cruft name", "cruft src uri" and a few more lines if you'll |
| 12 |
>> need to pass some extra parameters to configure/make/install. |
| 13 |
>> It'll build the package in a sandbox, then transfer it to destination, |
| 14 |
>> memorizing every change it did and preventing collisions and config |
| 15 |
>> overwrites. |
| 16 |
>> |
| 17 |
>> Just put that config script into an ebuild file and use portage to |
| 18 |
>> build it - as simple as it gets ;) |
| 19 |
> |
| 20 |
> If you have to learn to write anything, I suggest learning to write ebuilds |
| 21 |
> instead which will probably be a better long term solution. That way you |
| 22 |
> can reuse that knowledge in your Gentoo experience and you don't need |
| 23 |
> a cruft remover either because you can just emerge -C your program. |
| 24 |
> |
| 25 |
|
| 26 |
Ehm, that's what Mike was suggesting, albeit wittily :) |
| 27 |
|
| 28 |
m. |
Archives