Santiago Vila wrote:
> On Fri, 14 Jan 2005, Jay Berkenbilt wrote:
>
>> I've read Section 5.9.3 of the developer's reference and understand it
>> clearly. Is that still the best way to go?
>
> Not always, unfortunately. Very often, the upgrade will be smoother if
> you use empty dummy packages w
Hello,
I've been through a few iterations with this package on this list
implementing suggestions.
Please have a look at the latest incarnation if you could, and give me
any feedback.
Hopefully I'm getting closer ;)
Binary and source pkgs available at
http://www.cs.purdue.edu/homes/rstutsma/de
Santiago Vila <[EMAIL PROTECTED]> writes:
> On Fri, 14 Jan 2005, Jay Berkenbilt wrote:
>
>> I've read Section 5.9.3 of the developer's reference and understand it
>> clearly. Is that still the best way to go?
>
> Not always, unfortunately. Very often, the upgrade will be smoother if
> you use emp
> "ms419" == ms419 <[EMAIL PROTECTED]> writes:
ms419> mod-auth-kerb is a terrific Apache module to authenticate
ms419> connections using Kerberos; it even supports GSSAPI
ms419> negotiation (SPNEGO) - ie. single sign on authentication
ms419> using Apache2 & Kerberos!
ms41
Just take a look this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264231
Since libapache-* and libapache2-* share exactly the same code, it
should be a a multibinary source package.
Ghe Rivero
El sÃb, 15-01-2005 a las 14:27 -0800, [EMAIL PROTECTED] escribiÃ:
> mod-auth-kerb is a te
mod-auth-kerb is a terrific Apache module to authenticate connections
using Kerberos; it even supports GSSAPI negotiation (SPNEGO) - ie.
single sign on authentication using Apache2 & Kerberos!
I repackaged mod-auth-kerb for Apache2 & added some more documentation:
http://cgi.sfu.ca/~jdbates/moi
Hi, i am working on the orphaned package "hwtools" which i took after reading
it's description. the surprise came after unpacking, a strange directory
called tpqic02-support-1.9b seems to be a driver for a tape device with a few
utilities, i'm wondering why this driver is in this package, it s
On Fri, 14 Jan 2005, Jay Berkenbilt wrote:
> The recent thread on names of library packages on debian-devel made me
> decide that I made a mistake in naming one of my packages.
> Specifically, the vips7.10 source package creates four binary
> packages: libvips7.10, libvips7.10-dev, libvips7.10-too
On Fri, 14 Jan 2005, Jay Berkenbilt wrote:
> Renaming the packages now will create a minor nuisance: the small
> number of users of the package will have to learn a new name for the
> package, ftp-masters will have to remove these packages that they just
> approved, and the vips packages will have
Jay Berkenbilt <[EMAIL PROTECTED]> writes:
> The recent thread on names of library packages on debian-devel made me
> decide that I made a mistake in naming one of my packages.
> Specifically, the vips7.10 source package creates four binary
> packages: libvips7.10, libvips7.10-dev, libvips7.10-too
10 matches
Mail list logo