| 1 |
On 01/08/2013 11:24 PM, Douglas Freed wrote: |
| 2 |
> On Thu, Jan 3, 2013 at 5:23 AM, Zac Medico <zmedico@g.o> wrote: |
| 3 |
>> The CVS keyword expansion causes the ebuild digest to mutate during the |
| 4 |
>> commit. If we repoman could predict correctly emulate the CVS keywords |
| 5 |
>> expansion on the client side, then it could generate a correct Manifest |
| 6 |
>> in advance. However, that seems difficult given that the CVS keyword |
| 7 |
>> expansion contains a timestamp with 1 second precision. |
| 8 |
> |
| 9 |
> Thought: Do the CVS keyword expansion in repoman, and then feed the |
| 10 |
> expanded file to CVS for commit. This gives you a fixed file, which |
| 11 |
> you can then generate your manifest against. |
| 12 |
|
| 13 |
Yeah, I guess that will work, if we disable the keyword expansion on the |
| 14 |
CVS server (is it possible?). |
| 15 |
|
| 16 |
If we're going to rely on repoman to do all of the keyword expansion, |
| 17 |
then I guess we need to add support for committing in profile and eclass |
| 18 |
directories: |
| 19 |
|
| 20 |
https://bugs.gentoo.org/show_bug.cgi?id=390651 |
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Zac |
Archives