| 1 |
On Thursday 01 April 2004 11:38, Paul de Vrieze wrote: |
| 2 |
> On Thursday 01 April 2004 11:05, Spider wrote: |
| 3 |
> > please fix the darn Manifest files when you've been touching things. |
| 4 |
> > That includes when you remove files, when you modifiy patches (!) and |
| 5 |
> > others. |
| 6 |
> |
| 7 |
> I completely second this. You must use repoman. Only in very very few |
| 8 |
> special cases is it waranted not to use repoman. If repoman prevents you |
| 9 |
> from committing something, find out why and either have repoman fixed, |
| 10 |
> or fix your package. |
| 11 |
|
| 12 |
When removing files repoman won't update Manifest, that's bug number one, |
| 13 |
actually I think it will even not let you commit that update (rm'ed file). |
| 14 |
|
| 15 |
And now it also seems when using repoman you still need to verify everything |
| 16 |
by hand because you can't depend on it to do it properly. So far I've had |
| 17 |
nothing but trouble with it and it's never given me any helpfull comments, |
| 18 |
except for complaining about going out of business. |
| 19 |
|
| 20 |
So how does one regenerate the Manifest when repoman feels it's not needed? |
| 21 |
touch one of the non-changed builds and repoman commit or is there another |
| 22 |
way? |
| 23 |
|
| 24 |
Bart |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives