hi. i'm adopting eggdrop, while sitting in NM. i've got the latest version
of eggdrop building ok, after some heavy Makefile.in hacking, but lintian
is giving me this error:
-- snip --
E: eggdrop: shlib-with-non-pic-code usr/lib/eggdrop/modules/channels.so
N:
N: The listed shared libraries conta
hi. when i adopt a package, should i keep the changelog from the previous
maintainer?
--
__
| "the whole scale of cosmic dimensions are falling from my mouth
| in the description of a kiss of the interimlovers"
| - einsturzende neubaten, "interim"
are there any guidelines as to when i should split a package into several
smaller packages?
i maintain eggdrop, which is just under 2mb installed. about 450k of that
is documentation. should i think of splitting it off into an eggdrop-doc
package?
--
On Thu, 30 Nov 2000, Dave Baker wrote:
>
> Just out of the NM queue, I've put together some scsiadd packages and
> wondered if someone could take a quick look over them before I upload
> to make sure they're up to par.
>
> I've gone through the maint-guide process to build the packages, so
> the
a while back, it was mentioned that it's now possible to make source-only
package uploads. i'm quite interested in doing this, since i wouldn't have
to deal with building the package in my woody chroot, but could just
upload the source and let the autobuilders have at it.
so... can anyone enlighte
hi there. i have a slight problem... i have a package which depends on
tcl. problem is that dh_shlibdeps finds tcl8.2 installed, and sticks that
in the Depends: field. it would be better if it could depend on tclsh,
which is provided by the (many) different versions of tcl instead of being
bound to
hi. i'm adopting eggdrop, while sitting in NM. i've got the latest version
of eggdrop building ok, after some heavy Makefile.in hacking, but lintian
is giving me this error:
-- snip --
E: eggdrop: shlib-with-non-pic-code usr/lib/eggdrop/modules/channels.so
N:
N: The listed shared libraries cont
hi. when i adopt a package, should i keep the changelog from the previous
maintainer?
--
__
| "the whole scale of cosmic dimensions are falling from my mouth
| in the description of a kiss of the interimlovers"
| - einsturzende neubaten, "interim"
are there any guidelines as to when i should split a package into several
smaller packages?
i maintain eggdrop, which is just under 2mb installed. about 450k of that
is documentation. should i think of splitting it off into an eggdrop-doc
package?
--
___
On Thu, 30 Nov 2000, Dave Baker wrote:
>
> Just out of the NM queue, I've put together some scsiadd packages and
> wondered if someone could take a quick look over them before I upload
> to make sure they're up to par.
>
> I've gone through the maint-guide process to build the packages, so
> th
a while back, it was mentioned that it's now possible to make source-only
package uploads. i'm quite interested in doing this, since i wouldn't have
to deal with building the package in my woody chroot, but could just
upload the source and let the autobuilders have at it.
so... can anyone enlight
hi there. i have a slight problem... i have a package which depends on
tcl. problem is that dh_shlibdeps finds tcl8.2 installed, and sticks that
in the Depends: field. it would be better if it could depend on tclsh,
which is provided by the (many) different versions of tcl instead of being
bound t
On Thursday 29 November 2001 04:52 pm, Sean Dundon wrote:
> Hello,
> I just started with Linux, I have Potato 2.2r4. I was wondering if I
> could find some one who could give me a hand through things on a more
> personal basis. I have lots of those little annoying problems like
> mounting an
On Thursday 29 November 2001 04:52 pm, Sean Dundon wrote:
> Hello,
> I just started with Linux, I have Potato 2.2r4. I was wondering if I
> could find some one who could give me a hand through things on a more
> personal basis. I have lots of those little annoying problems like
> mounting and
14 matches
Mail list logo
