On 01/08/2013 11:49 PM, Duncan wrote:
> Zac Medico posted on Tue, 08 Jan 2013 23:36:59 -0800 as excerpted:
> 
>>> 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?).
> 
> If I'm reading him correctly, Douglas is suggesting to do the expansion 
> in repoman, so the keyword that are normally expanded aren't even there 
> to expand any longer.

I guess we could use the cvs -ko option [1] on all files. That's
apparently what prevents $Header expansion for $PORTDIR/skel.ebuild.

> Then expansion doesn't need to be disabled on the server, since the ebuild 
> has no expandable keywords to trigger it.  That leaves the ability to 
> still use the keywords intact, if there's a special-case need for them or 
> something.

The expanded form still contains the $Header string that triggers the
expansion though, so I we need to use the cvs -ko option or something
like it.

> Of course that assumes that the keywords are suitably distinct such that 
> they won't ordinarily be found in the pre-expanded lines.  Whether that's 
> actually the case or not I've no idea...

Well, I'd suggest to simply drop the keywords. Weren't we planning to
drop the CVS keywords for the git migration, anyway?

[1] http://www.cs.utah.edu/dept/old/texinfo/cvs/cvs_16.html#SEC55
-- 
Thanks,
Zac

Reply via email to