[Bug 627032] Review Request: w3c-linkchecker - W3C Link Checker

[bugzilla at redhat.com]

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=627032

--- Comment #6 from elad <el.il at doom.co.il> 2011-03-29 03:06:04 EDT ---
(In reply to comment #5)
> (In reply to comment #4)
> 
> (regarding upstream md5sum etc)
> > I'm not sure if it is a requirement, but it is recommended.
> 
> Where is it recommended?  This is the first time I've heard of such a
> recommendation.
> 
> (regarding placing files in /var/www)
> > This IS required, sorry.
> 
> Note that the packaging guidelines say "should", not "MUST".
The "not" is in capital letters, which made me think it is important. I'll ask
more experienced developers about it. 
> 
> > You won't need configuration for every web server, you
> > can select just few common ones
> 
> ...and if those config files are installed in proper locations, there either
> a) Needs to be a dependency on the servers that provide those dirs which is a
> no go because the software will run on command line without any web server, or
You can make sub-packages in your package, eg. w3c-linkchecker-apache that will
supply the configuration files for apache, and do so for every sever you like
(one is enough, if you don't want too many subpackages), and the main package
would only provide the command line application.
> b) The config files need to be in web server specific subpackages that have the
> dependencies which is IMO quite ugly, or
> c) This package would need to own those dirs, which is also quite ugly.
> 
C is not an option, it is against the guidelines.
> > or put a simple file somewhere in /usr/share
> > and write in a readme file or a manual that it should be copied to the
> > appropriate directory.
> 
> That's not what I personally would expect of a properly packaged application.
> 
That's was just an idea.
> So given the options above, my opinion remains that simply placing the script
> in /var/www/cgi-bin is a superior approach, even if it's a "should not" per the
> packaging guidelines.
> 
> > I'm sorry to hear that. Hope you'll find someone else to maintain it.
> 
> You wouldn't happen to be interested, would you?
As I'm not a packager yet (I'm doing unofficial reviews to prove that I am
"worthy"), I don't know how to take this review request. I'll try to ask
someone in #fedora-devel, to see if (and how) I can do that.

-- 
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.