Trying to make sense of all the X modular packages

[Daniel Stone]

On Thu, Nov 10, 2005 at 08:33:31PM -0800, Jeremy C. Reed wrote:
> As for later releases of "modular" X.org X11 as a whole: will all the 
> individual source tarballs be touched? new CVS tags? new version numbers?

Nope.

This is AIUI, but I'm pretty sure it's correct.

Tarballs with changes will get new versions rolled by their maintainers
if the maintainer wants.

The maintainers can then nominate given tarballs for the next release.
As most of the modules we have now don't have clearly-defined
maintainers, this will be largely automatic and probably done by the
release managers.

So, it's possible to have a module with a ton of changes, but keeping
the same tarball from one release to the next, if it's simply not ready
for a stable release.

> I am hoping that I can upgrade modular X.org six months from now and not 
> have to repackage over 30 packages again. I hope that only the downloads 
> will change will have actual content or code changes and that source that 
> never changes could just be reused. For example, if xf86vidmodeproto-2.2.1 
> never changes, I hope I don't have to repackage it.

Correct.  This will not change unless necessary.

> In other words, will X11R7.1 require repackaging of every component?

No.

> And next question: anyone working on README files? We have 30+ source 
> downloads that don't have any description what so ever. (Even most headers 
> aren't descriptive enough to get an idea what they are for.)

Not yet, no.  Patches gratefully accepted and all that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.x.org/archives/xorg-modular/attachments/20051111/926089ab/attachment-0001.pgp