Re: when and why did python(-minimal) become essential?
* Thomas Hood [Fri, Jan 20 2006, 10:32:06AM]:
> Matt Zimmerman wrote:
> > The compromise we struck with upstream was that we would not give
> > the user a system with a "broken" Python.
> So upstream objects to the separate packaging of python-minimal unless
> all of python is installed when python-minimal is installed (which in
> Ubuntu's case is: always) unless the user takes special action to
> prevent this. Hmm.
Just my 0.02€: that is upstream's deliberate decission, telling you not
to use Python for Essential-class code.
You simply cannot follow both targets, the "most blown full useable
environment" and "slim interpreter". Most of this thread is modern
alchemy, trying to cheat / find ways between them but not getting
Sometimes decissions must be made and in this case the rule should be:
stick to what you have or make best compromises when integrating new
stuff. Since a compromise (reduced python environment) is taboo, just
forget it. If we follow the latest shiny tool on the horizont, we should
integrate Java and .NET into base. With full dependencies, of course.
<Tolimar> Statler: Durchsuch mal die fortunes nach Aqua ;)
<Aqua> Tolimar, ich find nichts von den Sachen lustig
<Aqua> ihr habt ja sogar das reingegeben als ich gefragt wurde welche Xfree
version ich habe