Simon Josefsson wrote:
> >> > I see the following description dependency graph:
> >> >
> >> > +-----+
> >> > | |
> >> > shisa -> shishid -> shishi <-+
> >> > ^ ^ ^
> >> > | | |
> >> > shishi-common | shishi-dbg
> >> > |
> >> > shishi-doc
> >> >
> >> > So not even the description of the package most descriptions depend
> >> > upon is self-contained but depends on itself. Even though recursion
> >> > is nice, it does not have to be implemented in package descriptions.
> >> >
> >> > Please untie and release the descriptions
> >>
> >> Hi again. I'm not sure I understand what the problem is.
> I've changed it to:
>
> Package: shishi
> Description: Command line client for the Shishi Kerberos v5 implementation
> Package: shishi-common
> Description: Platform independent files for Shishi
> Package: shishi-doc
> Description: Documentation for Shishi
> Package: shishi-dbg
> Description: Debugging symbols for Shishi
> Package: libshishi0
> Description: Library for the Shishi Kerberos v5 implementation
> Package: libshishi-dev
> Description: Development files for the Shishi Kerberos v5 library
> Package: shisa
> Description: Administration utility for the Shishi Kerberos v5 KDC database
> Package: libshisa0
> Description: Library for the Shishi Kerberos v5 KDC database
> Package: libshisa-dev
> Description: Development files for the Shishi Kerberos v5 KDC database library
> Package: shishid
> Description: Kerberos v5 Key Distribution Center (KDC) Shishi server daemon
>
> How about it?
Much better. So Shishi is a Kerberos v5 implementation. Now it makes
sense at last.
Regards,
Joey
--
Experience is something you don't get until just after you need it.
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
