bryce at bryceharrington.org
Fri Nov 30 21:14:12 GMT 2007
On Fri, Nov 30, 2007 at 01:23:03PM +0100, Tormod Volden wrote:
> Unfortunately I was off-line yesterday, so I didn't read this and did
> some parallell work on it...
Hopefully we didn't duplicate efforts too much. I suspect we didn't,
since I focused more on structural stuff than the core git commands.
> I finally bit the bullet and installed git-doc, RTFM and without
> claiming that I am a git master, I now have got the git stuff sorted
> out better. I have attached a v4 (version clash with yours - maybe we
> should use source revision tool...) to XorgOnTheEdge.
Great, I'll check it out. I agree we probably should put this into
revision control since we're both working actively on it.
> It works fine except when there are missing Build-depends in Debian
> git, or when the debian/patches in Debian git are outdated and need a
> manual refresh. The script waits at strategic points, so you can do a
> ctrl-Z and fix these things. Maybe having a catalogue of needed fixes
> for each package would be a way.
One of the use cases I'm shooting for is unattended operation, so want
to have the ability to force things through so they can work completely
automated, and just mark failures as errors. The goal would to be to
build a table listing all the packages with very recent git head
packages, with green/red to indicate which built automatically, and
which will need further fussing to get them building properly.
Of course, the other use case is the same as yours - using the script by
hand to progress through to the points where failures occur.
So I figure we optimize for one use case (probably the latter manual
one, to save our fingers), and have options to handle the other case.
Anyway, for the full optimization case, I figure it makes sense to force
things through to completion, and bypass or eliminate anything that
would otherwise require manual intervention, even if it results in
somewhat improper packages. So I decided to just drop all patches. I'd
like to also force the git merge a bit more - I figure in general we
should just drop debian versions of anything outside debian/ in favor of
upstream. I'm unsure on how to do this, though.
> It can now build from upstream branches, example: auto-xorg-git ati
One other suggestion/question is if we can put a requirement to enter
the full driver name (e.g. xserver-xorg-video-ati instead of ati). The
reason is that it'd make it easier to use this script for a wider
variety of packages, that might otherwise get detected as drivers.
I added a '-p' flag to provide this capability, but would like it to
work this way by default without the -p flag.
More information about the Ubuntu-x