Gentoo Archives: gentoo-alt

From: Fabian Groffen <grobian@g.o>
To: gentoo-alt@l.g.o
Subject: [gentoo-alt] Re: Any procedure to test a quick patch to a package?
Date: Thu, 13 Dec 2012 09:06:21
Message-Id: 20121213073443.GX8220@gentoo.org
In Reply to: [gentoo-alt] Re: Any procedure to test a quick patch to a package? by "René Berber"
On 12-12-2012 15:24:04 -0600, René Berber wrote:
> On 12/12/2012 1:45 PM, Fabian Groffen wrote: > > > so, what you basically want is > > 1) a patch to the python-2.7.3 ebuild for cygwin > > 2) a new tar of that > > > > (see the ebuild for comments about what to comment out, it's really as > > simple as running ebuild ... prepare and tarring the result up) > > > > right? > > No. > > > If so, let's start with the patch that you need. > > I thought the log bits made it obvious, the bootstrap-prefix.sh just > started, its not using an ebuild, it just downloaded zlib, and built it, > then downloaded python-2.7.2-patched, and while building it the (trivial > to fix) error stops everything.
... and I told you how that tar was created, and thus what a good next step would be to help you further.
> I just want to know if there is a procedure to not start from the > beginning. The "patch" I want to do is to python-2.7.2-patched, > specifically Python-2.7.2/Modules/_io/_iomodule.c:172 which shouldn't > re-declare anything.
Just re-run the installer with identical input, and it will "resume". -- Fabian Groffen Gentoo on a different level

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
[gentoo-alt] Re: Any procedure to test a quick patch to a package? "René Berber" <r.berber@××××××××.org>