Re: Modularity questions for "traditional" RPM packaging

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

 



On 14 November 2017 at 09:50, Marek Skalický <mskalick@xxxxxxxxxx> wrote:
> Christopher píše v St 08. 11. 2017 v 22:33 +0000:
>> On Wed, Nov 8, 2017 at 2:27 PM Igor Gnatenko <ignatenkobrain@fedorapr
>> oject.org> wrote:
>> > On Wed, 2017-11-08 at 18:58 +0000, Christopher wrote:
>> > > Hi, I've been reading a lot lately about Fedora modularity, and
>> > I'm
>> > > still a
>> > > bit confused on some points.
>> > >
>> > > Is it necessary for maintainers to create modules for their RPM
>> > > packages?
>> > Yes.
>>
>
> First of all, I'm not modularity expert. Sharing only what I figured
> out during creation of module for my package.
>
>> When will they need to do this? And, how?
>> Do I need to create a module per-RPM?
>
> Not per-RPM. But
>
> " If you see that your module needs a common package (like net-tools),
> you shouldn’t bundle them either. They should be split into individual
> modules. "
>

This makes me a sad panda ;)

I get what you are saying but net-tools is a really bad package to
pick on given efforts to follow through with deprecating it!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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