| To: | Max Matveev <makc@xxxxxxxxx> |
|---|---|
| Subject: | Re: rpm dependencies |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Thu, 07 Nov 2013 14:40:29 -0500 |
| Cc: | nathans@xxxxxxxxxx, mgoodwin@xxxxxxxxxx, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <21115.57413.974649.418399@xxxxxxxxxxxx> (Max Matveev's message of "Fri, 8 Nov 2013 05:47:33 +1100") |
| References: | <21115.57413.974649.418399@xxxxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Max Matveev <makc@xxxxxxxxx> writes:
> [...] I can understand libmicrohttpd could be legitimate dependency
> (although I'd argue that if one doesn't give a damn about http
> access one should need it) but why create dependency on python-pcp
> and perl-PCP-PMDA? [...]
It's a judgement call as to how finely to subdivide the pcp packages.
To partition the dependencies further, we'd need at least three new
subpackages:
- pcp-pmwebd (for the libmicrohttpd user)
- pcp-python-tools (for pmatop, pmcollectl, etc.)
- pcp-perl-tools (for the pmdas)
It could get unsightly. Though at some point we might do this kind of
thing, say if in the future we want to segregate pure
agent/target-side stuff from clients.
- FChE
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | rpm dependencies, Max Matveev |
|---|---|
| Next by Date: | Re: rpm dependencies, Nathan Scott |
| Previous by Thread: | rpm dependencies, Max Matveev |
| Next by Thread: | Re: rpm dependencies, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |