packages requiring "httpd" as opposed to requiring "webserver"?
Robert P. J. Day
rpjday at crashcourse.ca
Thu Feb 20 20:21:04 UTC 2014
On Thu, 20 Feb 2014, Rahul Sundaram wrote:
> HI
>
>
> On Thu, Feb 20, 2014 at 11:11 AM, Robert P. J. Day wrote:
> that might be a *lot* of bug reports:
>
> $ repoquery -q --whatrequires webserver| wc -l
> 20
> $ repoquery -q --whatrequires httpd| wc -l
> 205
>
>
> You shouldn't do this blindly. Some packages specifically need
> httpd and not just any webserver. This needs to be analyzed and
> reported on a case by case basis. As you can imagine, this is a lot
> of careful analysis from the packager's perspective as well. I know
> and can ensure some package I maintain works with httpd. I don't
> know even know how to start some of the others much less actively
> test it for each release. This is why a lot of package maintainers
> just depend on httpd directly.
i realize that, which is why my later reply admitted that it's
entirely possible that many of those packages really depend on httpd.
i'm simply making an observation.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
More information about the users
mailing list