A few months back, I attempted to package TinyMUSH 3.0, but ran into some
trouble with a few clauses that seemed to imply something wasn't quite DFSG
free. I had submitted a report to the developers, and they expressed
interest in making it compliant. I haven't really done much with the package
sin
A few months back, I attempted to package TinyMUSH 3.0, but ran into some
trouble with a few clauses that seemed to imply something wasn't quite DFSG
free. I had submitted a report to the developers, and they expressed
interest in making it compliant. I haven't really done much with the package
sin
> > For a package I'd like to make, I need gdbm 1.8.0, while the current
> > maintainer has stated that he will not upgrade to this version, and that
> > if I need it I should package it myself. So, here I am, packaging the
> > library. What should I do to make sure that it does not interfere with
> > For a package I'd like to make, I need gdbm 1.8.0, while the current
> > maintainer has stated that he will not upgrade to this version, and that
> > if I need it I should package it myself. So, here I am, packaging the
> > library. What should I do to make sure that it does not interfere with
For a package I'd like to make, I need gdbm 1.8.0, while the current
maintainer has stated that he will not upgrade to this version, and that
if I need it I should package it myself. So, here I am, packaging the
library. What should I do to make sure that it does not interfere with the
regular gdbm
For a package I'd like to make, I need gdbm 1.8.0, while the current
maintainer has stated that he will not upgrade to this version, and that
if I need it I should package it myself. So, here I am, packaging the
library. What should I do to make sure that it does not interfere with the
regular gdb
> > I'm building a package that depends on gdbm 1.8.0, which is newer
> > than the version Debian uses. I notified the gdbm maintainer, but
> > have not received a response.
>
> Well, a response _was_ sent.
>
> | So; go ahead and include the non-shared gdbm1.8.
Terribly sorry about that... It ap
I'm building a package that depends on gdbm 1.8.0, which is newer than the
version Debian uses. I notified the gdbm maintainer, but have not received
a response. The source package, presumably because it's an uncommonly used
version of gdbm, contains the source to 1.8.0 which can be used during the
> > I'm building a package that depends on gdbm 1.8.0, which is newer
> > than the version Debian uses. I notified the gdbm maintainer, but
> > have not received a response.
>
> Well, a response _was_ sent.
>
> | So; go ahead and include the non-shared gdbm1.8.
Terribly sorry about that... It a
I'm building a package that depends on gdbm 1.8.0, which is newer than the
version Debian uses. I notified the gdbm maintainer, but have not received
a response. The source package, presumably because it's an uncommonly used
version of gdbm, contains the source to 1.8.0 which can be used during th
I will be packaging TinyMUSH 3.0 for Debian, and, having read all of the
relevent manuals (and some irrelevent ones), have noticed that this will
probably require some out-of-the-ordinary procedures, outlined below. I am
requesting that somebody with experience in resolving these matters, or at
lea
I will be packaging TinyMUSH 3.0 for Debian, and, having read all of the
relevent manuals (and some irrelevent ones), have noticed that this will
probably require some out-of-the-ordinary procedures, outlined below. I am
requesting that somebody with experience in resolving these matters, or at
le
12 matches
Mail list logo
