| Summary: | Move update-webkit-auxiliary-libs to Python | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Kevin Ollivier <kevino> | ||||
| Component: | WebKit Misc. | Assignee: | Kevin Ollivier <kevino> | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | Normal | CC: | aroben | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Attachments: |
|
||||||
|
Description
Kevin Ollivier
2008-04-10 18:58:40 PDT
Created attachment 20467 [details]
Moves update-webkit-auxiliary-libs to Python
Comment on attachment 20467 [details]
Moves update-webkit-auxiliary-libs to Python
As much as I love python, I'm not sure this is actually helpful, unless you plan to take over maintenance of this script. Currently I think adam does most of that. Assigning to Adam for review, if he likes it, we'll land it.
Well, either way, I'd really appreciate getting some sort of final decision on this. As I said, I was asked if I was interested in such a conversion by Darin, but if there isn't really interest in such a move, then I'd just like to know so I don't invest more time in it. FWIW, while I didn't intend to become the maintainer of this script, I was planning on making some improvements in terms of supporting multiple ports (e.g. wx, Win/Cairo, etc.) and compilers (e.g. VS7/8/9 versions of libs). Since a Python conversion was being talked about, I figured what better place to start than a script I'd be doing work on. ;-) (That's how I had intended to approach the transition, actually, moving on to scripts as I needed to work on them.) Comment on attachment 20467 [details]
Moves update-webkit-auxiliary-libs to Python
I'm going to say r-. We don't have a compelling reason to move all of our scripts to Python, and several of the developers that frequently work on the scripts would prefer that they remained Perl.
Okay, thanks, closing this ticket then. :) |