I'm not quite sure about it, but part of the entry under Dependencies on http://docs.openstack.org/developer/pbr/packagers.html might suggest that pip isn't a dep since 1.0. Please check that - dev-python/linecache2 seems to install without it.
While it is optional, it's still needed at times (bad packages mainly). Therefore I will keep it as a dep for now.
(In reply to Matthew Thode ( prometheanfire ) from comment #1) > While it is optional, it's still needed at times (bad packages mainly). > Therefore I will keep it as a dep for now. Sorry, could you clarify ? Cause the way I understand the note, "bad packages mainly" translates to "packages with unstated/automagical deps", so IOW packages with *ebuilds*, that need fixing, not such workarounds.
ebuilds won't merge because we block the net access and the like. This is for people using pbr locally to develop something (installing something to their home folder for instance)
(In reply to Matthew Thode ( prometheanfire ) from comment #3) > ebuilds won't merge because we block the net access and the like. This is > for people using pbr locally to develop something (installing something to > their home folder for instance) 1. shouldn't they know by themselves that they might need pip in such case ? 2. again, the note says "Since 1.0.0 we now document that dependencies should be installed before installing a pbr using package." 3. even if you disregard 2, that should be at most a conditional dep
(In reply to Matthew Thode ( prometheanfire ) from comment #1) > While it is optional, it's still needed at times (bad packages mainly). > Therefore I will keep it as a dep for now. there is nothing in the pbr package suggesting that pip is directly needed. Also the quoted notes say the same. If some badly packaged package needs pip the dep belongs there.
try pbr-1.8.1-r1
