OGS wrote:
> I'd suggest an install of the BrutefirDrc plugin also pulls down
> Brutefir and Python if these are not installed.
>
The plugin package has always had a dendency on brutefir, so it will be
installed if it isn't already. Don't need an explicit dep on python.
(Several core Fedora package require it, so it will always already be
installed.)
OGS wrote:
>
> It will also be very helpful to include the the sample* filters and
> null* pcm files to enable testing "out of the box" as you suggest in
> your post at the BrutefirDrc forum.
I already added them in the update I posted earlier.
Code:
--------------------
$ rpm -ql logitechmediaserver-plugin-BrutefirDRC | grep filters
/etc/squeezeboxserver/BrutefirDrc/filters
/etc/squeezeboxserver/BrutefirDrc/filters/null-65k48-l.pcm
/etc/squeezeboxserver/BrutefirDrc/filters/null-65k48-r.pcm
/etc/squeezeboxserver/BrutefirDrc/filters/sample_eq.txt
/etc/squeezeboxserver/BrutefirDrc/filters/sample_filter_and_eq.txt
/etc/squeezeboxserver/BrutefirDrc/filters/sample_filter_no_eq.txt
/etc/squeezeboxserver/BrutefirDrc/filters/sample_info.txt
--------------------
OGS wrote:
>
> Rob's idea of smb sharing the filters directory is also very good. I use
> a similar method where I bind this directory to a folder on a share I
> already have connected. This makes it easy to work with filters, but
> maybe a good description of how to do this is enough?
>
I can't create those directories 777 from installing the package. I'll
get my balls busted on security grounds.
There is always a bigger picture......
I have aspirations about getting some of the "free" software hosted in
the
CS repo, moved to "upstream" repos. The 3 packaged LMS plugins, (so
far),
are not just packaged for arm, they are also packaged for desktop
i686/x86_64. I'm not going to start putting "if arch arm; then do a
bunch of
insecure things" into the spec files and I'm sure as hell not going to
create directories 777 on all arches, when we have several LMS users
(non-ARM) who are "heavily involved" with upstream Fedora.
I don't need to be seen as the guy who doesn't give a fig about
security. If
we wanted to set back where we are now, that I've spent a year
packaging
stuff, and doing it in such a way that it is "compatible", (whenever
possible), with upstream guidelines, and that there are a bunch of
people
who trust me enough to run software I have packaged on their machines,
(and
again not just talking about CSOS ARM users), creating directories 777,
well, it's not going to happen. I can't stop what anyone does after
installing a package. Make the rootfs writeable by anyone. Fine! But it
won't be supplied to you that way. Or not by me, anyway!
What a user does after installing a package with permissions is nothing
to do with me. ;) I'm happy to put what Rob documented into a guide/FAQ
and put it on the CS website.
------------------------------------------------------------------------
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread: http://forums.slimdevices.com/showthread.php?t=99395
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
