| 1 |
On Fri, 20 Apr 2007 14:52:46 +0200 |
| 2 |
Fabian Groffen <grobian@g.o> wrote: |
| 3 |
|
| 4 |
> On 20-04-2007 15:45:00 +0300, Petteri Räty wrote: |
| 5 |
> > > I use it to make deltas of changes made in the tree, and apply |
| 6 |
> > > those deltas on the overlay I'm using. Without $Header: $ there |
| 7 |
> > > I have no way to actually see which version I'm dealing with, so |
| 8 |
> > > which revisions to retrieve for differences. |
| 9 |
> > > For that reason, I prefer as much files as possible in the tree |
| 10 |
> > > to have a $Header: $ somewhere, so I can easily sync, keeping my |
| 11 |
> > > local changes. |
| 12 |
> > |
| 13 |
> > Is the info you need in CVS/ ? |
| 14 |
> |
| 15 |
> That requires: |
| 16 |
> a) an up-to-date CVS tree checkout |
| 17 |
> b) a CVS tree (not a regular rsynced one) |
| 18 |
> c) parsing of the CVS/Entries file |
| 19 |
> |
| 20 |
> So in principle, yes I think it can be done using the CVS directory, |
| 21 |
> but I prefer not to. |
| 22 |
|
| 23 |
+1 on this one. |
| 24 |
|
| 25 |
I am writing some script to automate package building and use the |
| 26 |
Header field to detect CVS revision changes. I know I could do it with |
| 27 |
hash values, but then it would be harder to have builds from |
| 28 |
different revisions of the same ebuild file time ordered. |
| 29 |
|
| 30 |
Best, |
| 31 |
Yuri. |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives