Don Armstrong wrote: > I was prepared to answer the points earlier in this message, but I've > decided that beyond establishing a patern, they have no importance to > debian-devel Exactly, and (as I already said at least two times) my intent was to avoid this "GPL/illegal" discussion. > It's highly likely that there are other license and copyright irregularities > in the codebase as well.[1] I can only repeat what I wrote in my previous mail: you came to this conclusiong because you haven't found a pretty little Changelog in libmpeg2/ ? (and - once again - see my explanation about CVS repository) > No. What you need is on every single file in the libmpeg2 directory a > notification stating that this file was modified for i in *; do echo "/* file modified */" > $i; done Cool. > > Also: our libmpeg2 is NOT 0.3.1! It's a modified 0.2.x . > It's apparently a libmpeg2 0.2.1-CVS version, with totally unknown > modifications made to it: Why is it unknown? Anybody tried to block you from doing diff -u ? > These are the only two changelog entries regarding libmpeg2 that I > could find.[2] That's about all the change that took place in it. :) > And, yes, Debian does distribute diffs for all changes made to a > pristine upstream source. [At least, properly packaged packages do.] BTW, does anyone know where is the source of the "xega" (EGA X server) package in Debian Bo? Someone swallowed it, just as its maintainer, oe.hansen > The above is just a small slice of the issues which have caused Debian to shy > away from including mplayer. Is there any character for a half-faced smiley? :7 > > So live with it. > Debian, and the Free Software world in general has a nasty habit of > not living with it. It's your right to decide :) -- Gabucino MPlayer Core Team "not sure how we will proceed here - xine's potential in the video processing field is imho so great that i certainly don't want to miss the chance to work into that direction." - Guenter, xine developer
Attachment:
pgprNr8kUcGUz.pgp
Description: PGP signature