graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #02997
Re: [Question #179669]: Why aren't dependencies automatically pulled in?
Question #179669 on Graphite changed:
https://answers.launchpad.net/graphite/+question/179669
Status: Answered => Open
Xiong Chiamiov is still having a problem:
That's fair enough - I understand the splitting now.
But the lack of dependency management is frustrating! If you're going
to put up packages on the cheeseshop, they should run after you install
them! graphite-web absolutely needs Django, but doesn't install it,
which almost entirely defeats the point of using a package manager in
the first place. I need to download the requirements.txt in my
provisioning scripts, at which point I might as well just download the
entire tarball and forgo the packages.
> Try doing that on a production Solaris box that has no internet
access,
pip install --no-download
> where the sysadmins are sadistic BOFHs.
Why aren't the sysadmins managing packages on their boxes? I'd be a
BOFH to you, too, if you were fucking around with my machines.
--
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.