Re: GDBM 1.8

> > 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

Re: GDBM 1.8

> > 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

Re: GDBM 1.8

Jon Eisenstein <[EMAIL PROTECTED]> writes: > 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 s

GDBM 1.8

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

Re: GDBM 1.8

Jon Eisenstein <[EMAIL PROTECTED]> writes: > 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

GDBM 1.8

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