Hi John,
On 23 August 2013 00:36, John <phoenixoverride(a)gmail.com> wrote:
The final straw was when I just converted to Git and
discovered that he is
trying to run executables.
I think most of us agree using patch.exe was not the best decision.
However, creating a way to install dependencies locally, which also works
well for windows users - unfortunately, virtualenv and others don't work
too well for some windows workflows, I think was a sensible idea.
This is bloatware plain and simple I have seen the
number of externals go
from 2 to 17. Most of these are probably for one or two pet programs that
should never have been added to the project as they are niche programs.
I don't agree on this - the number of externals that /can be installed/ has
increased, but the only one required is BeautifulSoup. This is not
different from how things were before. Thanks to the new packaging system,
you are only asked to install them when required. Yes, they are typically
for one or two scripts, but calling them 'pet programs' is just nonsense -
the scripts DrTrigon has added (e.g. sum_disc/discussion summaries,
subster/dynamic page updating from an external source, catimages/smart(er)
image categorization based on content) are useful tools, even though Dr
Trigon might be the only one running them at the moment.
I would really like to see things streamlined and all
of the cruft removed
and get back to the nice library that we had.
Apart from the patch.exe issue, I', not really sure what there is to
streamline - the extra externals are only installed on demand and the new
scripts are not in the way of using other scripts.
Merlijn