First pass at X11R7.6 katamari list

Dirk Wallenstein halsmit at t-online.de
Thu Sep 23 02:17:12 PDT 2010


On Wed, Sep 22, 2010 at 06:30:01AM -0700, Dan Nicholson wrote:
> On Tue, Sep 21, 2010 at 9:58 PM, Alan Coopersmith
> <alan.coopersmith at oracle.com> wrote:
> > I haven't gone through yet to see which need new releases from git, but
> > this seems to be the current set of modules that are slated to become
> > the 7.6 katamari over the next month or so.
> 
> Sorry to hijack this thread, but I wanted to throw out a half baked
> idea I've had kicking around my head for a while. I'd like it if we
> could get the katamari set included as a jhbuild moduleset in the
> modular repo and then have modular released with the katamari. The
> idea being that the answer to "how do I build Xorg-7.6?" is to grab
> xorg-modular-7.6.tar.gz from
> http://xorg.freedesktop.org/releases/X11R7.6/ and use the included
> moduleset with jhbuild. While I'm aware that the preferred way to get
> X is through your distro, I still think it should be possible to
> easily get vanilla X.
> 
> What do you think? It would basically require you to turn this module
> list into a jhbuild moduleset (not a small amount of work, but just
> maintenance after the initial conversion), and to add a little bit of
> autotooling to modular (easy) so it can be disted at katamari time.

The moduleset posted here [1] contains module-ids and checkoutdirs that
correspond to the package-name.  With that moduleset it is possible to
just use sed to append a 'tag' attribute after each 'checkoutdir'
attribute to create a Xorg-7.6 moduleset from a module-list.txt file.
Some deps have to be removed to pull in only Xorg modules.
    $> xjh init
    $> xjh -m Xorg-7.6 build

A 'checkout' subcommand for x-jhbuild is high on my todo list, and it
would cover a subsequent branch creation after a checkout.  However, I
am planning a separate save/restore/checkout mechanism apart from that
provided through a moduleset where you just have module-ids mapped to
shas (one doesn't always want to pull when switching the state of
multiple repositories).  The shas in that file could also be tags.
    $> xjh init
    $> xjh checkout Xorg-7.6
    $> xjh build
All contained modules would be on a Xorg-7.6 branch, now.

I am still preparing a real release for x-jhbuild.  Just wanted to make
it a bit more 'project-like' -- the main script is dissected into a
library, style guides applied, etc.  And there is a status plug-in, a
git-like config-mechanism, and a one-shot install procedure (including
both JHBuild and Git-Python).  Coming soon...

Another thing I've been thinking about is an XML tool that can create or
transform modulesets.  It could create katamari modulesets but it might also
be able to create a moduleset from git-repositories located below the
init directory -- if you just want to track arbitrary unrelated
git-repositories and use tools like the status plug-in, or want to script
for multiple repositories.  But that is beyond the Xorg-7.6 deadline.

[1] http://lists.freedesktop.org/archives/xorg-devel/2010-July/010915.html

-- 
Greetings,
Dirk


More information about the xorg-devel mailing list