Since version 2.x.x. plowshare is not shipped with modules anymore. There
are two repositories. The main repository , with the core package, and a
new repository, with the modules .
Due the massive change of hosters, the modules are always beeing updated,
and a little tool "plowmod" deal with modules updates. This tool can
install and update the modules locally, which is much better than to
provide the modules inside the package.
So, upstream recommends to deal with "plowshare" core only, which it is
quite stable. And I agree.
So, the question is: Am I violating Fedora Packaging Guidelines if I do not
provide the modules into fedora repositories?
Sorry for possible english mistakes.
 - https://github.com/mcrapet/plowshare
 - https://github.com/mcrapet/plowshare-modules-legacy
GNU/Linux User: #471180
"O conhecimento é tristeza: aqueles que mais sabem são os que mais
profundamente devem lamentar a mais fatal verdade, a árvore do conhecimento
não é a da vida." (Da tragédia Manfred, de Byron e citado por Nietzsche em
"Humano, Demasiado humano")
On Dom, 2015-04-26 at 10:27 +0100, Ankur Sinha wrote:
> On Sun, 2015-04-26 at 09:25 +0100, Ankur Sinha wrote:
> > Sure. I'll send you a patch on the rpmfusion-devel list.
> Just out of curiosity - do you know why the package is in rpmfusion and
> not in Fedora? I couldn't find a review bug on the rpmfusion bug
No , but emulators normally are forbidden items on Fedora .
Sérgio M. B.
Obviously upstream support will mainly dictate this, but is there any
distro wide sense yet if one should consider Qt5 as the preferred
default over Qt4 for a given Fedora release?
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
The Ceph package ships some utilities that are not intended to be run by users.
1. There's one utility that prepares Ceph's object storage daemon and
that is at is in /usr/libexec/ceph/ceph-osd-prestart.sh . The systemd
unit file calls that with "ExecStartPre=".
2. There are some other utilities that are only used by udev, and
these are currently in /usr/bin. I was going to move these to
/usr/libexec , but someone brought up the point that all these files
are architecture-independent, so perhaps they should go into
I confess I've only seen /usr/libexec used for add-on utilities, but
now I'm curious.
Does it make more sense for these sort of scripts to live in
/usr/libexec, or in /usr/share?