| 1 |
On Tuesday 22 December 2009 19:21:21 Helmut Jarausch wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I have ebuilds fetching the source code directly from a repository |
| 5 |
> (be it CVS,SVN,HG,GIT,...) |
| 6 |
> I'd like to modify the .ebuild to enter compilation only if something |
| 7 |
> has been updated. |
| 8 |
> Is this possible, has somebody else tried to do so? |
| 9 |
|
| 10 |
You can't. |
| 11 |
|
| 12 |
The only things that trigger a recompile are the things you already know |
| 13 |
|
| 14 |
- version number change |
| 15 |
- USE flag change |
| 16 |
- mask change |
| 17 |
|
| 18 |
None of those things has occurred in your scenario, so a recompile will not |
| 19 |
happen. This is by design and you should leave it this way. |
| 20 |
|
| 21 |
I suppose you *could* examine the version number in the CVS checkout, compare |
| 22 |
it to the last built version and make a decision based on that. Two problems: |
| 23 |
|
| 24 |
1. Such version numbers cannot universally be relied upon |
| 25 |
2. Portage does not currently store this information in any way that I have |
| 26 |
found, so you will need to patch portage. |
| 27 |
|
| 28 |
It's best to just always recompile everything, which is what you do when you |
| 29 |
work with CVS code manually. |
| 30 |
|
| 31 |
I also asked the same question in the past - about e17 - the above is my |
| 32 |
conclusions. |
| 33 |
|
| 34 |
-- |
| 35 |
alan dot mckinnon at gmail dot com |
Archives