From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Help applying a qt patch
Date: Tue, 4 Dec 2007 23:03:39 -0500 [thread overview]
Message-ID: <e38d12ff0712042003t4a0e8055h3b52fc333a48a95@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10712041440v5a186dd1mb2c8add2ae014b71@mail.gmail.com>
On Dec 4, 2007 5:40 PM, Grant <emailgrant@gmail.com> wrote:
> I've set the ebuild up in an overlay and added:
>
> epatch ${FILESDIR}/qt-4.3.1-r1_gcc3.4_compile_fix.diff
mv ${FILESDIR}/qt-4.3.1-r1_gcc3.4_compile_fix.diff
/qt-4.3.1-r1_gcc3.4_compile_fix.diff
> http://bugs.gentoo.org/attachment.cgi?id=131080&action=view
>
> Could someone tell me what I'm doing wrong?
The patch overwrites the *ebuild*, not the *package files*
correct command:
/#patch -N qt-4.3.1-r1_gcc3.4_compile_fix.diff
(/# means root shell, root (/) directory)
--
Andrey Vul
int i;main(){for(;i["]<i;++i){--i;}"];read('-'-'-',i+++"hell\
o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
hail ioccc
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2007-12-05 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 22:40 [gentoo-user] Help applying a qt patch Grant
2007-12-05 4:03 ` Andrey Vul [this message]
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=e38d12ff0712042003t4a0e8055h3b52fc333a48a95@mail.gmail.com \
--to=andrey.vul@gmail.com \
--cc=gentoo-user@lists.gentoo.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