Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: libextractor -- Simple library for keyword extraction https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214087 ------- Additional Comments From mtasaka@xxxxxxxxxxxxxxxxxxx 2006-12-22 03:21 EST ------- Well, (In reply to comment #8) > > * For main package: > > ---------------------------------- > > Requires: plugin(%name) > > ---------------------------------- > > What I meant was main package (libextract) should require at least > > base plugin package (libextract-plugins-base). > I do not think so: > > 1. libextract works without plugins too. But because output is very > limited in this case, you can say that plugins are highly recommended > (*not* required) > > 2. libextract does not require the -plugins-base plugins but works > e.g. with the thumbnail plugin when e.g. a collection of images > shall be indexed > > Therefore, I use > Requires: plugin(%name) > > which satisfies 1. and allows users to install only the really needed > plugins (2.). My biggest worry is that when libextractor requires plugin(libextractor), I cannot tell in advance which package this Requires actually pulls to satisfy this dependency because plugin(libextractor) is provided more than one package. ... For me, this always pulls a same package: ----------------------------------------------------- [root@localhost i386]# yum --disablerepo=\*debug\* --disablerepo=\*dries\* --disablerepo=\*freshrpms\* install libextractor Loading "installonlyn" plugin Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package libextractor.i386 0:0.5.16-2.fc7 set to be updated --> Running transaction check --> Processing Dependency: plugin(libextractor) for package: libextractor --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package libextractor-plugins-pdf.i386 0:0.5.16-2.fc7 set to be updated --> Running transaction check Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: libextractor i386 0.5.16-2.fc7 LOCAL 70 k Installing for dependencies: libextractor-plugins-pdf i386 0.5.16-2.fc7 LOCAL 131 k Transaction Summary ============================================================================= Install 2 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 201 k Is this ok [y/N]: N Exiting on user Command Complete! ----------------------------------------------------- however, * I am not sure if yum always pulls -pdf package for everyone * and I am not sure if pulling -pdf package is what you expect if yum always pulls -pdf package. If there is no "best" idea as of what plugins main package should require for a minimal usage, you may want to remove plugin requirement as before. My idea is requiring -plugins-base package is convenient for libextractor users. How do you think? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review