| 1 |
I have to go now. I'll read your reply & answer tomorrow. Hopefully we can |
| 2 |
get this issue quickly sorted out. |
| 3 |
|
| 4 |
|
| 5 |
On Monday 30 July 2001 01:21, you wrote: |
| 6 |
> On Monday 30 July 2001 01:14, you wrote: |
| 7 |
> > On Sun, Jul 29, 2001 at 09:40:54PM +0300, Dan Armak wrote: |
| 8 |
> > > Hi all, |
| 9 |
> > > |
| 10 |
> > > My question got lost in the howto thread, so I'm reposting here. |
| 11 |
> > > |
| 12 |
> > > How can I override checksum checking/generation in an ebuild? Some |
| 13 |
> > > things e.g. the howto ebuilds need this, because they're auto-updated 5 |
| 14 |
> > > days a week and we obviously can't keep checksum lists for all |
| 15 |
> > > versions. Therefore the ebuild should only check that the archive |
| 16 |
> > > extracts with no errors. |
| 17 |
> > |
| 18 |
> > You cannot override the md5 checks. They exist to ensure archive |
| 19 |
> > integrity, which is a good thing. Right now, you need to create a new |
| 20 |
> > ebuild for each new package version, as the package version of the ebuild |
| 21 |
> > and the actual src archive should be equivalent. |
| 22 |
> |
| 23 |
> So do you want me to create a new ebuild 5 days a week? And the end-user |
| 24 |
> would have to 'emerge rsync' 5 days a week to emerge the latest version? |
| 25 |
> |
| 26 |
> Now, we (pm and I) have spoken to the linuxdoc.org guy, and he's agreed to |
| 27 |
> make archives with timestamps in their filenames. But, mirrors probably |
| 28 |
> won't be keeping more than two or three old versions. So again we need to |
| 29 |
> update *something* 5 days/week. |
| 30 |
> |
| 31 |
> What do you propose? |
| 32 |
> |
| 33 |
> (Someone should include MD5 checksums as a server-side function in the |
| 34 |
> http/ftp protocols. :-) |
| 35 |
|
| 36 |
-- |
| 37 |
|
| 38 |
-- |
| 39 |
Dan Armak |
| 40 |
Gentoo Linux Developer, Desktop Team |
| 41 |
Matan, Israel |
Archives