On Sat, Nov 22, 2003 at 12:00:12AM -0600, Andrew Gaffney wrote: > Gregory P. Smith wrote: > >>This is a common problem with mplayer. It isn't portage's fault. This > >>problem occurs because the MPlayer developers release a newer version of > >>the font tarball, but name it the same. Because of this, emerge has no > >>idea > > > >Yes it is portage's fault. portage needs to be modified to support > >ebuilds that can specify required files without a md5 and size for cases > >like this. > > > >Unless you like reanswering this question every three days and causing > >many peoples super long emerges to fail in the middle rather than > >completing when they leave the computer alone while it runs... > > This would cause the error to go away, but it would *not* fix the problem. > Portage would see the *old* tarball in /usr/portage/distfiles and assume it > was the *newer* file that it needed. While it may not cause much of a > problem (in this case), it still does not fix the issue.
Perhaps change this ebuild to always attempt to fetch the file? if the fetch fails (user not online?) try and used the cached copy. only dying if the file doesn't exist at all. It's only a font file. Presumably not too important and with the above strategy the user hopefully has a font file fetched at least on the same date as the mplayer sources they're trying to build? -- [EMAIL PROTECTED] mailing list
