[Bug 592487] Review Request: ffgtk - A solution for controlling Fritz!Box or compatible routers

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 13 14:19:52 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=592487

--- Comment #17 from Louis Lagendijk <louis at lagendijk.xs4all.nl> 2011-01-13 09:19:48 EST ---
(In reply to comment #16)
> You should ignore rpmlint complaints about missing documentation when there is
> no documentation to be had.  You shouldn't fabricate documentation or duplicate
> it from the main package just to make the complaint go away.
> 
Understood. 

> Perhaps you don't understand the distinction between the regular package
> dependencies and scriptlet dependencies.  Package dependencies simply need to
> be satisfied in order for the package to work, so rpm ensures that they are
> installed by the end of the transaction.  Scriptlets may run at other times
> (during the transaction, either before or after the package is installed,
> upgraded or removed) and so any dependencies they may have needs to be
> specified so that rpm will ensure those dependencies are present when the
> scriptlets run.  Or, to put it another way, simply having the package depend on
> something called in the scriptlets is not sufficient.
> 
Thanks for the heads up,I was indeed not aware of the differences. I am reading
the information I can find for this.

> The "many duplicates in files" issue refers to the duplicated documentation.
Thanks.

Re. the md5 inclusion: would it help if I make a separate libmd5 package? I
whipped up a quick autofoo configuration, so I could package this as a separate
package. I would not know what license to put in the spec file.... If that
would help I can add a simple check for libmd5 in ffgtk's config and be done
with it. comments?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the package-review mailing list