code duplication

[Chuck Robey]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julien Cristau wrote:
> On Sun, Jul 20, 2008 at 15:22:46 -0400, Chuck Robey wrote:
> 
>> I don't know git too terribly well.  I know if this was cvs, then you'd have
>> only one directory (all the filenames are dup'd) and only use cvs commands to
>> check out particular tags, you'd *never* duplicate like I see here, it'd be
>> unprofessional.  Git I can't talk about, I just don't know it very well.
>>
> This is completely unrelated to git, it's only about tarballs.  So I'm
> not sure what you're talking about.

I thought you were saying that they xf86- driver that needed the old parser
wasn't part of the most recent xorg, right or wrong?  If you need the old parser
only for an old driver, well, it seems to be a fairly simple thing to just
package up tars with different tags.  One tag means you need the latest, and
another tag (which for many dirs is the exact same source verions as the HEAD
tag, only being old for those dirs that need it) for one that has olden drivers.

Unless you're telling me that inside one single build you need both the new and
the old parser code?  If you don't need both at once, then you don't need to
have 2 separate dirs.  Manipulating tags isn't a really difficult thing, at
least it's not in cvs or subversion (I am too innocent of git to comment).  It's
not even a difficult thing to have variant tarball names reflecting differing
source tags.

If you DO need both at once (in a single build), then I'm wrong, I guess.

> 
> Cheers,
> Julien

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiDlagACgkQz62J6PPcoOnpvwCePLlivRqePyBpjWWFyZfPugus
jUUAoIGDPqtTh2KowVk4mngkbLWiykAO
=YcRO
-----END PGP SIGNATURE-----