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