public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: overseers@sourceware.org
Subject: newer versions of python and git on sourceware?
Date: Fri, 26 Dec 2014 13:32:00 -0000	[thread overview]
Message-ID: <20141221222748.GM12884@adacore.com> (raw)

Hello,

I have been adapting AdaCore's git hooks, the scripts we use as hooks
in AdaCore's git repository, to be able to use them with the
binutils-gdb.git repoisitory on sourceware. Ref:
https://www.sourceware.org/ml/gdb-patches/2014-11/msg00700.html

I've added all the features that our hooks were missing, and was
working on adapting them to support the version of Python and Git
installed on sourceware, but unfortunately, the features missing
with the versions currently installed are really too convenient
to do without ("with ... as ...", OrderedDict, git's %B format,
etc). So, we need Python 2.7 and Git 1.9.

What would be our options for newer versions of both being installed?
I would assume that installing newer versions directly in /usr/bin
or /usr/local/bin would be too risky, so perhaps another area?

To determine the amount of work that would be involved, I installed
both at ~/home/gdbadmin/git-hooks-support, and then hard-coded that
path into the scripts. Ideally, I would prefer a more generic path,
such as /usr/local/git-hooks-deps, so that I could at least hardcode
a path that's not tied to the gdbadmin account. But otherwise, if
people are OK with the python & git installed in gdbadmin's home,
then we can use that until sourceware's next big update...

Please let me know, I can do the actual install work, if that helps
(ie, if we were to go with /usr/local/git-hooks-deps, we could make
that directory owned by gdbadmin).

Thank you!
-- 
Joel

             reply	other threads:[~2014-12-21 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 13:32 Joel Brobecker [this message]
2014-12-26 14:12 ` Frank Ch. Eigler
2014-12-27  8:13   ` Joel Brobecker
2014-12-29 21:26     ` Frank Ch. Eigler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141221222748.GM12884@adacore.com \
    --to=brobecker@adacore.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).