https://bugzilla.redhat.com/show_bug.cgi?id=2499516

UW_Linux <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?([email protected])  |



--- Comment #10 from UW_Linux <[email protected]> ---
So their are two files that follows GPL license:

> libfm-extra-1.4.1-build/libfm-extra-1.4.1/src/gtk/exo/exo-marshal.c
> libfm-extra-1.4.1-build/libfm-extra-1.4.1/src/gtk/exo/exo-marshal.h

They belong to excluded components and are not included in the resulting binary
RPM. However, the upstream tarball only contains the GPLv2 text in COPYING and
is missing the LGPL-2.1 license text applicable to libfm-extra. A downstream
copy of the LGPL-2.1 text is therefore needed to be included until upstream
provides it.

> The dir one is not that pressing if nothing else is expected to co-own the 
> directory (don't remember if it would leave `%{_includedir}/libfm-1.0` folder 
> upon uninstall though).

After installing and uninstalling `libfm-extra-1.4.1-1.fc45.x86_64.rpm` and
`libfm-extra-devel-1.4.1-1.fc45.x86_64.rpm`, an empty `/usr/include/libfm-1.0`
is left. I think it should be addressed like (if I'm not mistaken):

```
%dir %{_includedir}/libfm-1.0
```

And I don't quite see the point to use a seperate symlink `/usr/include/libfm`
-> `/usr/include/libfm-1.0`. Sorry if I'm missing something, but I think it
would be better to directly use `/usr/include/libfm` instead of placing include
file under `/usr/include/libfm-1.0` and then creating a symlink...


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2499516

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202499516%23c10

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to