1 |
On 01/08/2013 11:36 PM, Zac Medico wrote: |
2 |
> On 01/08/2013 11:24 PM, Douglas Freed wrote: |
3 |
>> On Thu, Jan 3, 2013 at 5:23 AM, Zac Medico <zmedico@g.o> wrote: |
4 |
>>> The CVS keyword expansion causes the ebuild digest to mutate during the |
5 |
>>> commit. If we repoman could predict correctly emulate the CVS keywords |
6 |
>>> expansion on the client side, then it could generate a correct Manifest |
7 |
>>> in advance. However, that seems difficult given that the CVS keyword |
8 |
>>> expansion contains a timestamp with 1 second precision. |
9 |
>> |
10 |
>> Thought: Do the CVS keyword expansion in repoman, and then feed the |
11 |
>> expanded file to CVS for commit. This gives you a fixed file, which |
12 |
>> you can then generate your manifest against. |
13 |
> |
14 |
> Yeah, I guess that will work, if we disable the keyword expansion on the |
15 |
> CVS server (is it possible?). |
16 |
|
17 |
On second thought, why not just remove the CVS keywords from the |
18 |
ebuilds? If we do that, then repoman will automatically commit the |
19 |
Manifest along with the rest of the files (like it already does in git |
20 |
repositories). Weren't we planning to drop the CVS keywords for the git |
21 |
migration, anyway? |
22 |
-- |
23 |
Thanks, |
24 |
Zac |