Hi Ralf, I don't have much packages modified this way so I don't mind redoing those correctly. I've read your last paragraph and you're telling me to basically download all the sources that I need from CVS and to modify those directly. However, I can't see how this will help me with upgrade. Are you always using the same CVS tree for a specific application for each version? Otherwise said, if I have let say Apache 1.3.2 and moving to Apache 1.3.3 or even 1.4 (hey, it's just an example), is it under the same CVS tree that I'll be able to update with cvs update -Pd?
I also have a related question. Yesterday I compiled and installed the
ipfilter libraries in order to install ip_filter. Now, I want to modify Squid
in order to activate the ipf_transparent feature. I tried doing a openpkg
--rebuild <package_name> --define "option 1" -- define "option 2". However,
this is not working. I'm receiving message saying that the define macro does
not exist. Should it work?
And what about adding include path? My ipfilter libraries are under
/usr/include/ipfilter and I didn't find any way to tell openpkg to include this
directory (or any directory I should say). I don't want to copy everything
back to /openpkg/include...
These are newbies questions but I can't seems to find answers in the FAQ or
handbook.
Thank you.
Etienne
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Ralf S. Engelschall
Sent: Thu 4/21/2005 2:06 PM
To: openpkg-users@openpkg.org
Subject: Re: Upgraded RPM vs modified <apps>.spec
On Thu, Apr 21, 2005, Etienne-Hugues Fortin wrote:
> I have a machine that is running for over a year now with Openpkg. It was
> version 2.1. I have numerous packages installed this way and some of them
> are installed from source and have modified spec file.
>
> My question is how can I upgrade this server without causing too much
> problems? Does the upgrade already look for modified spec file?
No, it cannot know that you modified the .spec file. What you have to do
is (1) forward port your .spec changes to the newer OpenPKG 2.3 version
and rolling your own local set of .src.rpm files and then (2) do a
regular upgrade from OpenPKG 2.1 to 2.3.
> Does
> openpkg consider if the application has been installed from source or
> binary?
OpenPKG always just _installs_ software from binary RPMs. The source RPM
is just unpacked and used to build a binary RPM, even if one can use the
"openpkg rpm -i" command with source RPM similar to binary RPMs, RPM
actually does not remember them at all.
> Will it just erase everything in /openpkg/RPM/SRC?
If you "openpkg rpm -i" a source file or perform a "openpkg rpm
--rebuild" on a source file, the <prefix>/RPM/SRC/ is overwritten, yes.
Because both the <prefix>/RPM/SRC/ and <prefix>/RPM/TMP/ directories are
just used internally during "openpkg rpm --rebuild".
So, I guess you have made your changes directly in the <prefix>/RPM/SRC/
area. Hence you first have to figure out what changes you have actually
made. In the worst case just do a "openpkg rpm --define '_sourcedir
/tmp/openpkg/%{name}' --define '_specdir /tmp/openpkg/%{name}' -i
*.src.rpm" with the original OpenPKG 2.3 source RPMs and then do a
"diff -ru3 /tmp/openpkg/ <prefix>/RPM/SRC/ >/tmp/openpkg.diff" to
retrieve your changes. Then clear the <prefix>/RPM/SRC/ area and install
the OpenPKG 2.3 source RPMs into it with "openpkg rpm -i *.src.rpm"
and reapply your changes with "cd <prefix>/RPM/SRC; patch -p0 -b
</tmp/openpkg.diff" and manually resolve any conflicts in the files.
For the long-term I _strongly_ recommend you to _NOT_ edit .spec files
under <prefix>/RPM/SRC/ at all -- except for perhaps some trivial
changes. Instead checkout via Anon-CVS the OpenPKG sources, apply your
changes _there_ (means: edit the files even they cannot be checked-in to
openpkg.org) and roll your own set of OpenPKG 2.3 source RPMs from there
-- which in turn then can be used without any problems to upgrade any
hierarchy.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
<<winmail.dat>>
