Thanks!

cicku, good idea!


Ralf, plowshare is a command-line downloader/uploader for some of the most popular file-sharing websites.  Each module (written in bash) corresponds to a different sharing site.  The modules are downloaded via plowmod, from a oficial repository provided by upstream. But, the users can install a module provided by another user, if they want to. The modules are updated constantly and it is difficult to update the package at the same pace. So, providing a core package and let the users to update the modules is a better idea in my opinion. The modules are installed under ~/.config/plowshare/modules.d/


Jason, thanks! I could package the modules. But this is not a good ideia as explained above. The package will be quickly outdated. Perharps, before I mark it as stable. However, if necessary, I will submit a review request to a new package, that will contain the modules.

On Mon, Apr 13, 2015 at 1:52 PM, Jason L Tibbitts III <tibbs@math.uh.edu> wrote:
>>>>> "EM" == Elder Marco <eldermarco@gmail.com> writes:

EM> So, upstream recommends to deal with "plowshare" core only, which it
EM> is quite stable. And I agree.

Well, look at how clamav does it.  The package provides a snapshot of
the virus data so that we can ship _something_.  This will be updated
when freshclam runs.

EM> So, the question is: Am I violating Fedora Packaging Guidelines if I
EM> do not provide the modules into fedora repositories?

Perhaps read over
https://fedoraproject.org/wiki/Packaging:Guidelines#Packages_which_are_not_useful_without_external_bits

Personally, I would still ship a module package, but for that to work,
the software has to have a mechanism for local downloads to override
system-provided modules.

 - J<



--
Elder Marco
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")