Re: dbs package - should I upload it?
On 31 Jan 2001, Brian May wrote:
> I have created a very simple package to help maintain DBS
uh, um, er, oh, ah
The author(me) is flabbergasted. Wow.
> 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>?
As I am the author, it might be best for me to maintain it.
> It currently contains:
> 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.
I don't particularlly like what Ben has done with openldap and dbs. It
changes the api. However, having a central location for this, would get
> 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:
This is VERY VERY MONDO cool. Give your self a pat on the back, then go out
and have a beer.
>  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>.
Not possbile(on both counts) :)
>  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.
There are ways around this.
----BEGIN GEEK CODE BLOCK----
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <email@example.com> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----