On 12/14/2011 05:24 PM, Evan Martin wrote:
1) Is it intentional that I am unable to use software from upstream
like Django unmodified? Am I expected to only install software
from the Arch repositories, where it has been patched by Arch devs
to work on Arch? (See below for more on Django.)
I don't profess to speak for the Arch devs - so please take the
following as my opinion, not the "official Arch answer".
But as a long-time Arch user, my opinion would be that the answer to
both those questions is a) yes, and b) I don't really see that as a problem.
Many/most distros apply some patches to upstream software. Arch does as
well, but generally tries to do so as minimally as possible.
In addition, Arch tries to run as bleeding-edge software as possible.
That's resulting in the situation you're describing: Arch uses Python3,
but some upstream packages have not been upgraded for that yet. So Arch
packages need to be temporarily patched to get around that. Otherwise
the packages will be broken. Seems like a reasonable reason to apply a
patch to me.
Also, I think the general intention with Arch is that you will install
software from packages in the repositories (or the AUR). It's not
generally expected (or supported) for you to randomly install software
directly from source code.
So probably the "Arch way" to solve the issue posed in your question
above would be:
* Use ABS to get a copy of the Arch PKGBUILD for whatever package is in
question
* Create your own copy/version of that PKGBUILD and tweak as needed to
support whatever non-standard functionality you're trying to achieve
* Build the package and install
* Realize that you're on your own from here on out. If you're running a
non-standard version of a package, then the responsibility for
supporting it / fixing incompatibilities & bugs is yours. You can't
expect that your non-standard package will automatically remain
compatible with all future updates to the standard Arch packages.
Dissent welcome.
HTH,
DR
