Re: RFC: Alternative -devel packaging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2018-08-07 at 11:33 -0400, Adam Jackson wrote:
> Consider a library like libGL. At runtime, you want the drivers it
> might load to be installed. But when building an application, you
> just
> need the library itself. If the drivers themselves have non-trivial
> dependencies, the buildroot is more likely to fail to compose.
> 
> The problem, in a sense, is that the devel package requires the
> package
> providing the API library, _and_ said required package requires the
> drivers. What if instead you had (in pseudo-spec):
> 
> %package devel
> Requires: %{name}-sdk
> 
> %package sdk
> 
> %package libs
> Requires: foo-drivers
> 
> where -libs and -sdk have identical %files, but -sdk has automatic
> provides for library sonames turned off (so it never satisfies a
> runtime dependency). This would duplicate some content on the
> mirrors,
> but not the installed system, and it would let you compose a
> buildroot
> with only the API surface you link against.

In my point of view, in opencv package , sdk should require -devel not
the inverse   

%package sdk
Requires: %{name}-devel

or doc contains the sdk examples : 
%package        doc
Summary:        docs files
Requires:       %{name}-devel = %{version}-%{release}

In Virtualbox package, I put part of sdk in devel sub-package and the
other part in pyhton2-%{name}

%files devel                                               
%{_libdir}/virtualbox/sdk
%exclude %{_libdir}/virtualbox/sdk/bindings/xpcom/python 

%files -n python2-%{name}                                    
%{_libdir}/virtualbox/*.py*
%{python2_sitelib}/virtualbox  
%{python2_sitelib}/vboxapi*  
%{_libdir}/virtualbox/VBoxPython2_7.so
%{_libdir}/virtualbox/sdk/bindings/xpcom/python

in resume I do not have any sdk sub-package , and or put that files on
docs or in devel dependent on importance ... 

> ---
> 
> Is this all dodging the issue that nothing agrees what Recommends:
> means? And that nobody's compose tools or comps files really
> understand
> what drivers they want, and that propagating that information is an
> unbounded task? Well, yeah, a bit. I still think it'd solve a real
> problem, I'm just wondering if the idea is too ugly to consider.
> 
> - ajax
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin
> es
> List Archives: https://lists.fedoraproject.org/archives/list/devel@li
> sts.fedoraproject.org/message/CHZR6OMICCL3Y6V7OFPV7MR62CSQY77C/
-- 
Sérgio M. B.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/SGVTVIRZNAZ4KLJECPSUQZR3TDNY6Q5P/




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux