Bug 28048 - Account request for X-JHBuild
Summary: Account request for X-JHBuild
Status: RESOLVED WORKSFORME
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: New Accounts (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL: http://lists.freedesktop.org/archives...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 00:52 UTC by Dirk Wallenstein
Modified: 2010-07-14 04:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
gpg pubkey (1.65 KB, text/plain)
2010-05-10 00:52 UTC, Dirk Wallenstein
Details
ssh pubkey (390 bytes, text/plain)
2010-05-10 00:53 UTC, Dirk Wallenstein
Details

Description Dirk Wallenstein 2010-05-10 00:52:58 UTC
Created attachment 35538 [details]
gpg pubkey

I am currently working on X-JHBuild and was wondering if it qualifies
for a fd.o repo. I've already added hooks for jhbuid commands, and the
cwd-module behavior is taking on shape. There's an ACLOCAL fix.
Comment 1 Dirk Wallenstein 2010-05-10 00:53:58 UTC
Created attachment 35539 [details]
ssh pubkey
Comment 2 Dirk Wallenstein 2010-05-10 11:40:19 UTC
Name : Dirk Wallenstein
Email : halsmit@t-online.de
Account : dirkwall
Comment 3 Tollef Fog Heen 2010-05-30 01:11:23 UTC
What is the relation between X-JHBuild and JHBuild?  From mailing list posts it looks like a wrapper around JHBuild and I'm not sure why this is considered appropriate for freedesktop.org rather than just being folded into JHBuild itself?

Please enlighten me.
Comment 4 Dirk Wallenstein 2010-05-30 03:33:42 UTC
(In reply to comment #3)
> What is the relation between X-JHBuild and JHBuild?  From mailing list posts it
> looks like a wrapper around JHBuild and I'm not sure why this is considered
> appropriate for freedesktop.org rather than just being folded into JHBuild
> itself?
> 
> Please enlighten me.

Yes, it's a wrapper.
It is appropriate because of all the parts that are specifically tailored for
use with freedesktop.org. It's a container for every special processing that
might be necessary and it is possible to distribute specific examples, plug-ins
and other source code like shell utility functions with it.

It is easy to introduce new features like cwd-module and repo-group local
configuration, change the default moduleset repository and facilitate access to
it. Introduce special hooks und plug-ins (suid the Xserver, start the Xserver).
Initialize a configuration with special values. Add special processing if the
repo-group is a supermodule. And all this can be done in a timely manner
without disturbing other use cases, with other build systems and/or vcs.

I try to improve JHBuild where it makes sense, but with this wrapper there will
be a very convenient, extensible build system in a few weeks.
Comment 5 Tollef Fog Heen 2010-07-14 02:49:02 UTC
Hi,

have you been in touch with jhbuild upstream to see if they're interested in merging your changes there?  I really do think that's a much better approach than having a separate wrapper.
Comment 6 Dirk Wallenstein 2010-07-14 04:17:51 UTC
(In reply to comment #5)
Hi,
Actually, this is not just a wrapper anymore. I'm steering it towards
becoming more of a meta-git that makes use of JHBuild. With scripting
possibilities across multiple repositories.
There aren't too many X.org specific parts (depcomp, moduleset, config)
and I can externalize them. I already thought about using Sourceforge,
as my other project is there, too. It's probably better to host it in a
more general location.
I'm doing a release currently and set it up after that.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.