dbs package - should I upload it?
Hello,
I have created a very simple package to help maintain DBS
source[1].
It basically works, but I still need to write documentation (the man
page has "still to be written" as the only informative text) for it,
and I imagine many improvements will still be possible.
Is anyone interested in this? Should I upload it to Debian? Would
anyone be more interested in maintaining it then me <grin>?
It currently contains:
/.
/usr
/usr/bin
/usr/bin/dbs-edit-patch
/usr/share
/usr/share/dbs
/usr/share/dbs/dbs-build.mk
/usr/share/dbs/file2cat
/usr/share/doc
/usr/share/doc/dbs
/usr/share/doc/dbs/README.Debian
/usr/share/doc/dbs/copyright
/usr/share/doc/dbs/changelog.Debian.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/dbs-edit-patch.1.gz
where dbs-build.mk and file2cat have been copied from the openldap
source. A package could "build-depend: dbs" and use this file instead
of including a separate copy for each DBS package.
As a sample run of how dbs-edit-patch[2] can be used, assume I want to
edit the 021_debian patch of Heimdal. I would proceed as follows:
[549] [snoopy:bam] ~/source/notmine/heimdal-0.3d >dbs-edit-patch -t/tmp 021_debian
Extracting source heimdal-0.3d.tar.gz ... successful.
Applying patch 001_replay ... successful.
Applying patch 002_libvers ... successful.
Applying patch 010_openssl ... successful.
Applying patch 011_sharedlibs ... successful.
Applying patch 012_maildir ... successful.
Applying patch 013_cache ... successful.
Applying patch 014_krb5-config ... successful.
Applying patch 015_ftp ... successful.
Applying patch 020_missingconf ... successful.
Copying heimdal-0.3d to heimdal-0.3d-old ... successful.
Applying patch 021_debian ... successful.
edit files under /tmp/021_debian/heimdal-0.3d as required, then
execute /tmp/021_debian/dbs_update_patch to save the results.
Technote: dbs-edit-patch extracts all patches before 021_debian into
/tmp/021_debian/heimdal-0.3d, copies the result to
/tmp/021_debian/heimdal-0.3d-old, and applies the last patch
021_debian (if it exists). Also, it creates a shell archive which will
create the diff between the old and new directories:
[550] [snoopy:bam] ~/source/notmine/heimdal-0.3d >ls -l /tmp/021_debian
total 12
-rwxr-xr-x 1 bam users 112 Jan 31 13:31 dbs-update-patch*
drwxr-xr-x 14 bam users 4096 Jan 31 13:31 heimdal-0.3d/
drwxr-xr-x 14 bam users 4096 Jan 31 13:31 heimdal-0.3d-old/
[551] [snoopy:bam] ~/source/notmine/heimdal-0.3d >cat /tmp/021_debian/dbs-update-patch
#!/bin/sh
diff -ruN /tmp/021_debian/heimdal-0.3d /tmp/021_debian/heimdal-0.3d-old > ./debian/patches/021_debian
Any comments?
Note:
[1] I hope to avoid flame-wars as to if DBS is a good/bad idea. I hope
I am not being too optimistic here <grin>.
[2] ideally you wouldn't have to specify a temp directory, and it
could be created under the source directory instead, however
dpkg-source would try to include this directory in the diff file,
which is not good. I didn't think deleting the directory was a good
idea either.
--
Brian May <bam@debian.org>
Reply to: