----- Original Message -----
From: "Vít Ondruch" <vondruch(a)redhat.com>
To: ruby-sig(a)lists.fedoraproject.org
Sent: Thursday, October 1, 2020 12:02:02 PM
Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 01. 10. 20 v 11:47 Pavel Valena napsal(a):
> ----- Original Message -----
>> From: "Vít Ondruch" <vondruch(a)redhat.com>
>> To: ruby-sig(a)lists.fedoraproject.org
>> Sent: Thursday, October 1, 2020 11:31:10 AM
>> Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
>>
>>
>> Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
>>
>>> On 30/09/2020 21:33, Pavel Valena wrote:
>>>> Hello,
>>>>
>>>> following on my previous email (bellow), I'm working on
regenerating
>>>> the list of packages `ruby-rails` group in Koschei.
>>>>
>>>> I've done some fixes to package resolving in my script (I'm left
with
>>>> 3 unresolved /ambiguous/ packages as well), and got current list:
>>>>
https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
>>
>> I think there is missing rubygem-mysql2, which might not appear
>> anywhere, because it is just optional, but we should not forget to
>> include it in the list. For the similar reason, it would be nice to keep
>> rubygem-mongo on the list.
> Hmm, but if it's not in the buildroot, should we concern ourselves with it?
> Or do we care for weak dependencies the same? I could add those explicitly
> (Recommends -> Require for those builds), or could be just on some
> "Includelist" WDYT?
I think there should be some initial list of packages we do care about,
this should be probably:
ruby
Not sure about ruby itself. Rails could theoretically run on any ruby runtime, right?
Anyway there's not much harm to have it there, if you insist. I'm simply missing
the point, ... now I realized. We don't have a `ruby` Koschei group. Maybe that's
something we want instead?
rubygem-rails and actually everything what appears in the Gemfile of
fresh RoR app
Ok, good idea. Although we currently don't have the asset pipeline (webpacker).
and some DB adapters:
rubygem-mysql2
rubygem-mongo
rubygem-pg (mongo got somehow pulled in, but it is just by coincidence
I'd say).
Yes, I think this corresponds to comps group. I'll take all packages from there.
>> And ruby itself should definitely be on the list.
> Well, isn't `ruby` other group? I've opted for `rubygems-` packages only.
I think we were talking about RoR group, which might not be just about
rubygems. Actually, we might be missing js-jquery for example. There
used to be also some other js- dependencies required by RoR app.
Right, let me check other runtime packages installed freshly with 'Ruby on Rails',
or @rubyonrails (that might cover all usecases above).
V.
Pavel