> [EMAIL PROTECTED] (joost witteveen) writes:
>
> > > 5. Conflicts & Dependencies for hamm packages
> > >
> > [..]
> > >
> > >The hamm libfoo package has to depend on libc6 and has to conflict
> > >with libfoo-dev and libc5-dev.
> >
> > Are you sure here? I'd say you mean this:
> >
>
[EMAIL PROTECTED] (joost witteveen) writes:
> > 5. Conflicts & Dependencies for hamm packages
> >
> [..]
> >
> >The hamm libfoo package has to depend on libc6 and has to conflict
> >with libfoo-dev and libc5-dev.
>
> Are you sure here? I'd say you mean this:
>
> The hamm libfoo p
> 5. Conflicts & Dependencies for hamm packages
>
[..]
>
>The hamm libfoo package has to depend on libc6 and has to conflict
>with libfoo-dev and libc5-dev.
Are you sure here? I'd say you mean this:
The hamm libfoo package has to depend on libc5 and has to conflict
with libfoo
> On Jun 20, Helmut Geyer wrote
> :
> : 1. Run time packages
> :
> : A package providing a shared library has to support both C library
> : packages, libc5 and libc6 based libraries. This must be done using
> : two Debian packages, each depending on the correct C library
> :
On Jun 20, Helmut Geyer wrote
:
: 1. Run time packages
:
: A package providing a shared library has to support both C library
: packages, libc5 and libc6 based libraries. This must be done using
: two Debian packages, each depending on the correct C library
: package.
: T
Hello!
I incorporated the changes mentioned by Mark Eichin.
Furthermore I noticed that there were several issues that have not
been handlied by this proposal, so I added several sections.
These tell how to handle dependences and conflicts, source packages
and bugfixes for bo. This is a lot of new
Hello!
I incorporated the changes mentioned by Mark Eichin.
Furthermore I noticed that there were several issues that have not
been handlied by this proposal, so I added several sections.
These tell how to handle dependences and conflicts, source packages
and bugfixes for bo. This is a lot of new
7 matches
Mail list logo
