On Dec 28, 2012, at 2:58 PM, Jakub Bogusz wrote:
> On Sat, Dec 08, 2012 at 12:48:55AM +0200, Elan Ruusamäe wrote:
>> hi
>>
>> https://spdx.org/licenses/
>>
>> perhaps we should use identifiers what that page uses.
>>
>> if yes, then i'll do mass update of all specs master branches, update
>>
On Sat, Dec 08, 2012 at 12:48:55AM +0200, Elan Ruusamäe wrote:
> hi
>
> https://spdx.org/licenses/
>
> perhaps we should use identifiers what that page uses.
>
> if yes, then i'll do mass update of all specs master branches, update
> adapter and rpmlint with the licenses list.
"License" is mea
On Dec 28, 2012, at 11:04 AM, Elan Ruusamäe wrote:
> hi
>
> what's the opinion of using (for example) "BR:
> pkgconfig(gsettings-desktop-schemas)" instead of
> "BR gsettings-desktop-schemas-devel"
>
> i find it pretty convinient to fill deps this way, as mostly configure.ac
> requires those p
On 28.12.2012 18:54, Jakub Bogusz wrote:
But it's less convenient for developers, to map individual BRs to
"human"/RPM package names.
is there good way to map pkgconfig name to rpm name?
good start would be if .pc file path would be printed then could rpm -qf it
from manual doesn't seem there's
On Fri, Dec 28, 2012 at 06:04:09PM +0200, Elan Ruusamäe wrote:
> hi
>
> what's the opinion of using (for example) "BR:
> pkgconfig(gsettings-desktop-schemas)" instead of
> "BR gsettings-desktop-schemas-devel"
>
> i find it pretty convinient to fill deps this way, as mostly
> configure.ac requir
hi
what's the opinion of using (for example) "BR:
pkgconfig(gsettings-desktop-schemas)" instead of
"BR gsettings-desktop-schemas-devel"
i find it pretty convinient to fill deps this way, as mostly
configure.ac requires those pkg-config names, not exact (rpm)packages
as for example, a build
