code duplication

[Adam Jackson]

On Sun, 2008-07-20 at 15:44 -0400, Chuck Robey wrote:
> 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.

The intel driver includes a copy of some version of the parser and modes
code it's known to work with, for the benefit of being compilable
against older (like 1.1 era) X servers.  If you're building against that
old of a server, then the driver build uses its internal copy of the
parser and modes code.  If you're building against something recent,
then it doesn't.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20080721/86a0f564/attachment.pgp>