Re: Updating scanners and filters in Debian stable (3.1)
On Thu, Oct 14, 2004 at 09:47:02PM +0200, Marc Haber wrote:
> On Mon, 11 Oct 2004 12:09:01 +0100, paddy <paddy@panici.net> wrote:
> >On Sun, Oct 10, 2004 at 02:50:35PM +0200, Marc Haber wrote:
> >> The clean way would be to build .deb files from the downloaded
> >> plugins, and to install them via the package management.
> >
> >I don't believe that everything can, will and should go into package
> >management. (although that may be the answer in this case).
> >
> >I can only imagaine that such debs would best live on volatile.
>
> I didn't think about uploading the debs in the first place. They would
> be built locally on the target machine and then installed; their sole
> purpose being to register the installed files with the package
> management.
Strange. I originally read you as meaning this, and I think I can see
that in my first paragraph. I suspect I wrote the second one later.
While this solution may be preferable for some uses, I think what bothers
me is the lack of a simpler solution. Is there really compelling reason
why all such files _must_ go into package-management? What currently happens
with other packages? (for example where do system-wide mozlila plugins go?
is f-prot wrapped in a .deb like this when its installed?)
I'd love a packaged system where random users and programs could install
software, but, unless I've missed something, debian is not such a system.
I'm not familiar with the exact details of the nessus setup, but I'm imagining
that these downloads are automated, not triggered by an apt-get or whatever,
that is: not under interactive admin control.
I think I'll take this conundrum over to fhs-devel, see what folk there say.
Regards,
Paddy
--
Perl 6 will give you the big knob. -- Larry Wall
Reply to: