pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/40290: multimedia/mediatomb doesn't install example config.xml
The following reply was made to PR pkg/40290; it has been noted by GNATS.
From: "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: agc%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost,
pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/40290: multimedia/mediatomb doesn't install example config.xml
Date: Mon, 29 Dec 2008 14:06:39 -0500
Lets try this again, as you missed the point of the original email.
Matthias Scheler wrote:
> On 29 Dec 2008, at 18:49, Jared D. McNeill wrote:
> > I don't understand; why would it write to that file if it already
> > exists (see above)?
>
> Because it has a web interface that can be used to change the
> configuration.
As far as I can tell you can only manipulate the mediatomb database,
which has nothing to do with config.xml.
> >> > The rc.d script should also give the option of overriding the
> >> > username and group passed to the mediatomb binary.
> >>
> >> The user and group name can be set at built time.
> >
> > That's a pretty poor workaround Matthias, you should still be able
> > to override it with mediatomb_flags (which is not possible today
> > unless you edit the rc.d script by hand).
You haven't addressed this point.
> > FYI, the Ubuntu package for mediatomb-daemon has the following
> > features:
> >
> > * Installs a default config file to /etc/mediatomb/config.xml
>
> Which they can only do because they don't allow you to set things
> like the installation path or the configuration directory.
Please explain to me why we can't do that as well.
> > * Installs a startup script to /etc/init.d/mediatomb
>
> The "mediatomb" package contains a startup script. If your system
> is configured accordingly it will automatically be copied to
> "/etc/rc.d" during installation.
Yes I am aware. Their startup script doesn't hard code the usernames,
which was mentioned in the rest of the email that you cut off.
None of the concerns in this PR have been addressed.
Cheers,
Jared
Home |
Main Index |
Thread Index |
Old Index