https://bugzilla.redhat.com/show_bug.cgi?id=1644268
Parag AN(पराग) <panemade(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|panemade(a)gmail.com |nobody(a)fedoraproject.org
Flags|fedora-review? |
|needinfo?(carmenbianca@fedo |
|raproject.org) |
--- Comment #9 from Parag AN(पराग) <panemade(a)gmail.com> ---
Thanks for your quick reply.
I will drop myself from this review but if you need any help with this package
review do write here.
About you point
(In reply to Carmen Bianca Bakker from comment #8)
As for renaming the package to mythes-eo: That will make hyphen-eo a
subpackage of mythes-eo and thus explicitly depend on mythes-eo's
dependencies, which is not desirable. The best course of action then would
be to maintain two separate packages, but that would be a little silly for a
single upstream.
No that will not happen that way. e.g. See
https://src.fedoraproject.org/rpms/hunspell-be/raw/master/f/hunspell-be.spec
file. Do you think hyphen-be explicitly depend on hunspell-be's dependencies?
No it will not.
Just See,
$ rpm -q --requires hunspell-be
hunspell
$ rpm -q --requires hyphen-be
hyphen
Try installing hyphen-be only, I don't see hunspell will get installed.
Dependencies resolved.
===============================================================================
Package Arch Version Repository Size
===============================================================================
Installing:
hyphen-be noarch 1.1-16.fc29 fedora 11 k
Installing dependencies:
hyphen x86_64 2.8.8-10.fc29 fedora 29 k
Transaction Summary
===============================================================================
Install 2 Packages
Total size: 40 k
Installed size: 62 k
Downloading Packages:
[SKIPPED] hyphen-2.8.8-10.fc29.x86_64.rpm: Already downloaded
[SKIPPED] hyphen-be-1.1-16.fc29.noarch.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installed: hyphen-2.8.8-10.fc29.x86_64
Installing : hyphen-2.8.8-10.fc29.x86_64 1/2
Running scriptlet: hyphen-2.8.8-10.fc29.x86_64 1/2
Installed: hyphen-2.8.8-10.fc29.x86_64
Installed: hyphen-be-1.1-16.fc29.noarch
Installing : hyphen-be-1.1-16.fc29.noarch 2/2
Installed: hyphen-be-1.1-16.fc29.noarch
Running scriptlet: hyphen-be-1.1-16.fc29.noarch 2/2
Verifying : hyphen-2.8.8-10.fc29.x86_64 1/2
Verifying : hyphen-be-1.1-16.fc29.noarch 2/2
Installed:
hyphen-be-1.1-16.fc29.noarch hyphen-2.8.8-10.fc29.x86_64
The package, as it's currently written, doesn't actually end up creating a
super-eo package---only the two subpackages.
Yes. I can see that. As there is no %files section so main package named
super-eo is not getting generated but only the subpackages binary rpms.
But I cannot find link/relation between the super-eo package name with
mythes-eo or hyphen-eo packages.
Maybe some other Sponsor want to accept such super-eo package....
--
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