<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Fri, 2010-04-09 at 06:11 -0700, Dan Nicholson wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Thu, Apr 8, 2010 at 11:22 PM, Yaakov (Cygwin/X)
<<A HREF="mailto:yselkowitz@users.sourceforge.net">yselkowitz@users.sourceforge.net</A>> wrote:
> On 2010-04-08 08:14, Dan Nicholson wrote:
>>
>> Huh, I hadn't noticed that. I think we should demand that you have the
>> version with the .pc file once there's a release. For the very few
>> people who are going to attempt to build the sgml documentation, I
>> think they can be bothered to grab a newer doctools package.
>
> That would be easier, and indeed the first version of my patch did just
> that, but Gaetan pointed out that this would cause a regression if macros is
> updated but not doctools. Whether or not that is acceptable as a tradeoff
> for the functionality of using pkg-config needs to be decided.
As long as someone makes a release of the doctools, I'd be willing to
make that sacrifice.
1. The number of people actually building the sgml docs is likely
extremely small and probably is encompassed by x developers trying to
make a katamari release and a handful of distro packagers. I think
they can be bothered to update one more package that has 0
dependencies.
2. The gain in proper versioning outweighs the loss of backwards
compatibility in my mind.
3. The time when people will be attempting to build the docs is likely
just before or after the next Xorg release. They'll be wanting to
download the new doctools for the updated entities anyway.
</PRE>
</BLOCKQUOTE>
I don't have objections in this case to somewhat break compatibility. I routinely test for such a scenario when making changes as I have been reminded that changes and new features in macros should not adversely affect current or previous versions of clients. There is some leeway here as long as it does not just plain break and is easy to figure out. It's a judgement call. <BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
--
Dan
_______________________________________________
<A HREF="mailto:xorg-devel@lists.x.org">xorg-devel@lists.x.org</A>: X.Org development
Archives: <A HREF="http://lists.x.org/archives/xorg-devel">http://lists.x.org/archives/xorg-devel</A>
Info: <A HREF="http://lists.x.org/mailman/listinfo/xorg-devel">http://lists.x.org/mailman/listinfo/xorg-devel</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>