wordpress and wordpress-mu don't work well when you're first starting to
use them: the configuration can't access its files at
/usr/share/wordpress{,-mu} due to SELinux. What do I need to do to write
an SELinux policy and push it upstream so that others don't run into
this problem by default?
--
Ian Weller <ianweller@xxxxxxxxx>
GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36
Attachment:
pgp3GmzJ4qXnu.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
