I recently had to rebuild both courier-imap and postfix from source to include support for MySQL. Although both are currently working, I have encountered several problems: 1. I downloaded courier-imap-3.0.7-3.3.src.rpm but when I built the binary RPMs, they were created as (non-root user) courier-imap-3.0.7-1.suse920.i586.rpm and show up as v3.0.7-1 in YaST. The spec file contains the correct 3.0.7-3.3 version. The postfix version remained postfix-2.1.5-3.2 though I had to manually search the SuSE FTP site to find the v3.2 source. 2. The installed binaries of courier-imap-3.0.7-1 are NOT marked with an "-i-" in YaST and hence YoU attempts to update them which would then overwrite the MySQL support. I tried to change or remove them from YoU but was unable to change the "Action" column. This means I can no longer use YoU at all unless I want to reinstall all binaries created from source afterwards. Questions/Suggestions: 1. How can I remove binaries created from source from YoU, i.e., manually force them to "-i-" or at least override YoU insistence on updating them? 2. How can I correct the version number in courier-imap? 3. Suggestion: When SuSE builds binaries, why not go for an "everything but the kitchen sink" approach, such as including MySQL and PostgreSQL support, thus enabling them to remain properly updateable via YoU? (When I rebuilt courier-imap to include MySQL, it created an additional binary RPM: courier-imap-mysql-3.0.7-1.suse920.i586.rpm which seems to be a good approach should I decide to install an "everything but the kitchen sink" binary but do not want, for example, MySQL support.) Thank you, Lucky Leavell
On Tuesday 29 March 2005 09:02 am, Lucky Leavell wrote:
3. Suggestion: When SuSE builds binaries, why not go for an "everything but the kitchen sink" approach, such as including MySQL and PostgreSQL support, thus enabling them to remain properly updateable via YoU? (When I rebuilt courier-imap to include MySQL, it created an additional binary RPM: courier-imap-mysql-3.0.7-1.suse920.i586.rpm which seems to be a good approach should I decide to install an "everything but the kitchen sink" binary but do not want, for example, MySQL support.)
Try Gentoo if you want easily customized packages. :) With regards to the RPM thing, I'd generally just change the name in the .spec file to courier-danny or similar, which both served to denote that the package was my customized version and to protect if from name conflicts with YOU. --Danny
The Tuesday 2005-03-29 at 10:02 -0500, Lucky Leavell wrote:
I recently had to rebuild both courier-imap and postfix from source to include support for MySQL. Although both are currently working, I have encountered several problems:
1. I downloaded courier-imap-3.0.7-3.3.src.rpm but when I built the binary RPMs, they were created as (non-root user) courier-imap-3.0.7-1.suse920.i586.rpm and show up as v3.0.7-1 in YaST. The spec file contains the correct 3.0.7-3.3 version. The postfix version remained postfix-2.1.5-3.2 though I had to manually search the SuSE FTP site to find the v3.2 source.
2. The installed binaries of courier-imap-3.0.7-1 are NOT marked with an "-i-" in YaST and hence YoU attempts to update them which would then overwrite the MySQL support. I tried to change or remove them from YoU but was unable to change the "Action" column. This means I can no longer use YoU at all unless I want to reinstall all binaries created from source afterwards.
You must have done something wrong, I think. When I compile something and install my rpm, Yast shows it with a padlock icon, it doesn't ever touch it again. I generally don't use the "spec" way, I use the lazy system: checkinstall, with very few exceptions. If I recompile a source package from SuSE, same version, I make my rpm version to be ...-999, so that YOU will not offer upgrades, mine is always newer. For example, I created a dummy free-ttf-fonts-1.0-999.i386.rpm. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
Danny Sauer
-
Lucky Leavell