Hello
> > 'packagesearch' is a package which uses a plugin architecture. Each
> > plugin provides a way to search for packages, e.g. doing a full text
> > search, searching by filenames or orphaned packages. All plugins are
> > shipped together with the main application in a single
> > package. Ho
On Fri, 03 Aug 2007 22:16:35 +0200, Benjamin Mesing <[EMAIL PROTECTED]> said:
> Hello, the latest message on debian-devel-announce made me rethink my
> decision for the dependencies for my package 'packagesearch'.
> Having read the policy again and again and also through the recent
> debian-deve
I don't know if this is in line with policy, but I would split the
plugins to one package per plugin, then let each of those packages
provide "packagesearch-plugin", and let packagesearch depend on
"packagesearch-plugin".
On 8/3/07, Don Armstrong <[EMAIL PROTECTED]> wrote:
> On Fri, 03 Aug 2007, B
On Fri, 03 Aug 2007, Benjamin Mesing wrote:
> As for 'packagesearch', even if no additional package is installed,
> there is always the full text search available - so the package by
> itself is useful. Thus there is no need to *Depends:* on deborphan
> or apt-file. Also, I could imagine a 'usual'
Benjamin Mesing wrote:
> * a plugin architecture package (which provides merely the
> framework for additional functionality) without any additional
> is useless by itself so it requires at least one plugin.
> According to the policy wording this should qualify for a
>
Hello,
the latest message on debian-devel-announce made me rethink my decision
for the dependencies for my package 'packagesearch'.
Having read the policy again and again and also through the recent
debian-devel thread [1], I am not sure whether to use *Recommends* or
*Suggests*.
'packagesearch'
6 matches
Mail list logo
