[Pkg-lustre-maintainers] Plans for pkg-lustre
Goswin von Brederlow
brederlo at informatik.uni-tuebingen.de
Thu Jul 19 08:57:10 UTC 2007
as you might have seen I already checked in some changes but I wanted
to ask for feedback before doing any more.
So here is what I want to do:
- Build in seperate build dir instead inside the source.
The build process in lustre has no proper clean target so changes
remain and poison the diff.gz [done].
Alternatively we could put the lustre.tar.gz soruce into the source
and unpack it before patching and building. And remove the source tree
completly in clean.
- Rewrite the patch-debian-ver/patch-vanilla-ver
The lustre patches are seperated and listed in the series files. They
are also shared between different kernel versions. I would like to
keep the seperate patches and series files have the apply/unapply
scripts use them.
This way we save space where patches are shared between kernel
versions and we can simply copy the files instead of applying them in
turn and pulling a diff at the end. No need to Build-Depend on kernel
- Remove lustre source from the svn, put it seperate and remove the -<version>
I don't think we want to create a new lustre-<version> for every lustre
release in svn. That would grow out of proportions quite quickly.
I'm not even sure we should track lustre developement at all. It
should be enough to track the debian dir, where all our work should
be. One would then just dump that into a lustre source or dump the
lustre.tar.gz file into it (see above) and build.
If we keep the unpacked lustre source in our svn we should keep it in
a lustre dir (without -<version>) so only one copy is there and only changes
are saved. Not a full copy for every version.
More information about the Pkg-lustre-maintainers