* Re: [gentoo-dev] New Python eclasses -- a summary and reminder
[not found] <20130211012056.3df19cc5@pomiocik.lan>
@ 2013-02-24 19:52 ` Sebastian Pipping
2013-02-24 20:00 ` Michał Górny
0 siblings, 1 reply; 2+ messages in thread
From: Sebastian Pipping @ 2013-02-24 19:52 UTC (permalink / raw
To: gentoo-dev, Michał Górny
Looks like great work so far.
On 11.02.2013 01:20, Michał Górny wrote:
> Secondly, I'd like to make it clear that the old python.eclass is
> 'almost' deprecated. We're in process of converting the in-tree
> packages to use the new eclasses but that's a lot of work [3].
>
> [..]
>
> [3]:http://dev.gentoo.org/~mgorny/python-r1/conversion.xhtml
I wonder what would be the best way to help with conversion for devs
with a few hours to contribute?
- Where does one go for peer review and how many eyes should be on
related commits?
- Should package "owners" be contacted in all cases?
- Are there any conversion sprints already or in the future?
Best,
Sebastian
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [gentoo-dev] New Python eclasses -- a summary and reminder
2013-02-24 19:52 ` [gentoo-dev] New Python eclasses -- a summary and reminder Sebastian Pipping
@ 2013-02-24 20:00 ` Michał Górny
0 siblings, 0 replies; 2+ messages in thread
From: Michał Górny @ 2013-02-24 20:00 UTC (permalink / raw
To: gentoo-dev; +Cc: sping
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Sun, 24 Feb 2013 20:52:45 +0100
Sebastian Pipping <sping@gentoo.org> wrote:
> Looks like great work so far.
>
>
> On 11.02.2013 01:20, Michał Górny wrote:
> > Secondly, I'd like to make it clear that the old python.eclass is
> > 'almost' deprecated. We're in process of converting the in-tree
> > packages to use the new eclasses but that's a lot of work [3].
> >
> > [..]
> >
> > [3]:http://dev.gentoo.org/~mgorny/python-r1/conversion.xhtml
>
> I wonder what would be the best way to help with conversion for devs
> with a few hours to contribute?
Write docs ;). We need more complete, cleaner docs.
> - Where does one go for peer review and how many eyes should be on
> related commits?
I guess #gentoo-python would be a good place. Look for me or floppym
especially.
> - Should package "owners" be contacted in all cases?
Well, I assumed that packages in Python herd can be converted without
contacting other maintainers. For other packages, I opened a bug.
> - Are there any conversion sprints already or in the future?
No. To be honest, I dislike unnecessary rush. The migration is a good
moment to find bugs in Python ebuilds and fix them. Well, definitely
better than 'review Python-related code' bugs :P.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-02-24 20:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20130211012056.3df19cc5@pomiocik.lan>
2013-02-24 19:52 ` [gentoo-dev] New Python eclasses -- a summary and reminder Sebastian Pipping
2013-02-24 20:00 ` Michał Górny
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox