Re: Packaging a library with binaries
On Thu, 2010-06-10 at 09:47 +0200, Joachim Breitner wrote:
> Hi,
I'm replying to the list also. Hope that's ok.
> Am Mittwoch, den 09.06.2010, 18:00 -0430 schrieb Ernesto
> Hernández-Novich:
> > I'm going to package ghc-events.
> >
> > As a library, it allows reading of GHC 6.12.1 event logs and later, so
> > as usual I'll create libghc6-ghc-events-*. However, it also includes an
> > executable named show-ghc-events, useful to dump the event log to text.
> >
> > I wonder if a separate package is needed for that executable or if it
> > makes sense to include it as a part of libghc6-ghc-events-dev.
>
> we have both in the archive. For example, libghc6-wash-dev contains
> wash2hs (I assume that only people developing software against the wash
> library will need that program), while haskell-debian puts its binaries
> in haskell-debian-utils, as they are useful independent of
> libghc6-debian-dev.
>
> So the question you’ll have to answer is: Is show-ghc-events useful for
> people who do not want to write code against the ghc-events-library, or
> not? (Judging from your e-mail, I’d guess it deserves its own package)
I'm not really sure yet :-)
I don't know of any other applications using ghc-events besides
threadscope. I suppose show-ghc-events could be used as a debugging aid
while developing over ghc-events and also as a standalone application
but, why dump event logs to text when you can use threadscope?
I'm leaning towards adding it to libghc6-ghc-events-dev.
--
Ernesto Hernández-Novich - @iamemhn - Unix: Live free or die!
Geek by nature, Linux by choice, Debian of course.
If you can't aptitude it, it isn't useful or doesn't exist.
GPG Key Fingerprint = 438C 49A2 A8C7 E7D7 1500 C507 96D6 A3D6 2F4C 85E3
Reply to: