Samuel Rakitničan wrote:
>> Submit a PR upstream to fix it, and use that patch to change it locally.
> So I did, upstream accepted it, but then it applied old location again. As
> it is noted in patch description for compatibility reasons. Now
> application installs on both locations.
>
> Should
> Submit a PR upstream to fix it, and use that patch to change it locally.
So I did, upstream accepted it, but then it applied old location again. As it
is noted in patch description for compatibility reasons. Now application
installs on both locations.
Should I remove now this files from the ol
It's not a huge deal, appstream searches both locations. Metainfo is best,
but a low priority fix IMHO. Richard
On 25 Jan 2018 14:42, "Neal Gompa" wrote:
On Thu, Jan 25, 2018 at 9:39 AM, Samuel Rakitničan
wrote:
> Hi,
>
> I have a package where upstream installs Ap
On Thu, Jan 25, 2018 at 9:39 AM, Samuel Rakitničan
wrote:
> Hi,
>
> I have a package where upstream installs AppData file in /usr/share/appdata,
> but the Fedora Packaging Guidelines says it should be installed to
> /usr/share/metainfo. I am wondering how to approach this; sh
Hi,
I have a package where upstream installs AppData file in /usr/share/appdata,
but the Fedora Packaging Guidelines says it should be installed to
/usr/share/metainfo. I am wondering how to approach this; should I submit a PR
upstream, should I change it locally or should I leave it unchanged
