From: Amin <raihan@citech-bd.com>
To: linux-newbie@vger.kernel.org
Subject: Re: How do you apply patches to source code?
Date: Mon, 26 May 2003 19:40:22 +0600 [thread overview]
Message-ID: <1043.1053956422@localhost.localdomain> (raw)
In-Reply-To: Message from Ken Moffat <ken@kenmoffat.uklinux.net> of "Mon, 26 May 2003 13:42:35 +0100." <Pine.LNX.4.53.0305261333460.3342@reg_kipling>
In message <Pine.LNX.4.53.0305261333460.3342@reg_kipling>, Ken Moffat writes:
> On Mon, 26 May 2003, Robert wrote:
>
> > I have recently obtained the source code to an application as a .src.rpm
> > file. I have unbundled the code into /usr/src/RPMS/SOURCES. There are a
> > whole lot of .patch.bz2 files in the directory, as well as the main .tar.bz
> 2
> > file.
> >
> > How do I compile the program with the patches?
> >
> > I realise this is probably an easy one, but I can't find any documentation
> > about applying patches.
> >
> > Robert.
> >
>
> I believe that every .src.rpm has a file telling rpm how to build it,
> maybe called specfile, and there is some option you give to rpm to build
> this (see `man rpm').
On slightly older systems, this command is
rpm --rebuild package.src.rpm
On newer systems, it's
rpmbuild --rebuild package.src.rpm
Try the latter first. Notice that you never have to see the
contents of the source rpm file. You only need to run the
above commands on it. Everything is automatically taken
care of.
> Of course, if you _want_ to build it by hand for some reason, you
> first need to unpack the .tar.bz2 (probably with
> tar -xvjf filename.tar.bz2), then cd into the directory it creates and
> run `bzcat ../patchname.patch.bz2 | patch -p1' for each patch, then
> build it as normal (typically ./configure ; make ; make install) -
> you'll want to see what options configure will support or need.
>
> But, you probably still need the specfile or whatever to tell you in
> what order the packages should be applied.
Logically, the specfile should specify rules for
automatically applying patches, or what would be the
convenience (to the user) of having the patches?
>
> Sorry I can't be more help, but `rpm' has broken on the only box I've
> got it on.
>
> Ken
HTH,
Yawar Amin
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-05-26 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 11:03 How do you apply patches to source code? Robert
2003-05-26 12:42 ` Ken Moffat
2003-05-26 13:16 ` Robert
2003-05-26 20:36 ` Ken Moffat
2003-05-26 13:40 ` Amin [this message]
2003-05-26 13:52 ` J S
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=1043.1053956422@localhost.localdomain \
--to=raihan@citech-bd.com \
--cc=linux-newbie@vger.kernel.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