Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net

well, set LD_LIBRARY_PATH does the trick
shoudn't postfix-install do that on it's own?

%install
LD_LIBRARY_PATH=$(pwd)/lib sh postfix-install -package -non-interactive 
install_root=%{buildroot} config_directory=%{postfix_config_dir} 
meta_directory=%{postfix_daemon_dir} 
daemon_directory=%{postfix_daemon_dir} 
shlib_directory=%{postfix_shlib_dir} 
command_directory=%{postfix_command_dir} 
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
sendmail_path=%{postfix_command_dir}/sendmail 
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
readme_directory=%{postfix_readme_dir} || exit 1


Am 12.02.2015 um 11:20 schrieb li...@rhsoft.net:

has somebody an idea for the chicken egg problem that postfix-install
in the %installof a RPM-spec can't load the shared libraries which are
built but not installed at that moment?

+ sh postfix-install -non-interactive
install_root=/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-1.fc21.20150212.rh.x86_64
config_directory=/etc/postfix meta_directory=/usr/libexec/postfix
daemon_directory=/usr/libexec/postfix command_directory=/usr/sbin
queue_directory=/var/spool/postfix data_directory=/var/lib/postfix
sendmail_path=/usr/sbin/sendmail newaliases_path=/usr/bin/newaliases
mailq_path=/usr/bin/mailq mail_owner=postfix setgid_group=postdrop
manpage_directory=/usr/share/man
sample_directory=/usr/share/doc/postfix-3.0.0/samples
readme_directory=/usr/share/doc/postfix-3.0.0/README_FILES
bin/postconf: error while loading shared libraries:
libpostfix-global.so: cannot open shared object file: No such file or
directory
bin/postconf: error while loading shared libraries:
libpostfix-global.so: cannot open shared object file: No such file or
directory
_

%build
CCARGS=-fPIC -DNO_NIS -DNO_NISPLUS -DNO_EAI -DNO_LMDB -DNO_CDB
-DNO_LDAP -DNO_PGSQL -DNO_SQLITE -DHAS_PCRE -I%{_includedir}/pcre
-DHAS_MYSQL -I%{_includedir}/mysql -DUSE_TLS -DUSE_SASL_AUTH
-DUSE_CYRUS_SASL -I%{_includedir}/sasl
-DDEF_CONFIG_DIR=\\\%{postfix_config_dir}\\\
-DDEF_META_DIR=\\\%{postfix_daemon_dir}\\\
AUXLIBS=-lpcre -L%{_libdir}/mysql -lmysqlclient -lm -L%{_libdir}/sasl2
-lsasl2 -lssl -lcrypto -Wl,-z,now -Wl,-z,relro,-z,noexecstack
%{__make} %{?_smp_mflags} -f Makefile.init makefiles shared=yes
CCARGS=${CCARGS} AUXLIBS=${AUXLIBS} DEBUG= OPT=%{optflags}
-Wno-comment -fno-strict-aliasing
%{__make} %{?_smp_mflags} CCARGS=${CCARGS} AUXLIBS=${AUXLIBS}
DEBUG= OPT=%{optflags} -Wno-comment -fno-strict-aliasing

%install
sh postfix-install -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1
install -c auxiliary/rmail/rmail %{buildroot}%{_bindir}/rmail


Re: rpmbuild and shared=yes

2015-02-12 Thread Peter
On 02/12/2015 11:20 PM, li...@rhsoft.net wrote:
 has somebody an idea for the chicken egg problem that postfix-install
 in the %installof a RPM-spec can't load the shared libraries which are
 built but not installed at that moment?

I changed it to make non-interactive-package and it works just fine
without the library issues:

make non-interactive-package \
   install_root=$RPM_BUILD_ROOT \
   config_directory=%{postfix_config_dir} \
   daemon_directory=%{postfix_daemon_dir} \
   command_directory=%{postfix_command_dir} \
   queue_directory=%{postfix_queue_dir} \
   data_directory=%{postfix_data_dir} \
   sendmail_path=%{postfix_command_dir}/sendmail.postfix \
   newaliases_path=%{_bindir}/newaliases.postfix \
   mailq_path=%{_bindir}/mailq.postfix \
   mail_owner=%{postfix_user} \
   setgid_group=%{maildrop_group} \
   manpage_directory=%{_mandir} \
   sample_directory=%{postfix_sample_dir} \
   readme_directory=%{postfix_readme_dir} || exit 1


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
[ Charset windows-1252 converted... ]
 
 Am 12.02.2015 um 14:12 schrieb Wietse Venema:
  li...@rhsoft.net:
  well, set LD_LIBRARY_PATH does the trick
  shoudn't postfix-install do that on it's own?
 
  You MUST NOT invoke postfix-install directly.
  You MUST use make install as described in the INSTALL instructions
 
 besides that SPEC is derived from Redhat ones years ago using make 
 install seems to change the whole semantic of what is happening in the 
 %install section

The Postfix installation procedure as documented installs Postfix
without the problems that you keep reporting.

The RELEASE_NOTES say at the top of the file, to avoid massive
frustration I will not repeat that text here, but summarize
it as YOU IGNORE INSTRUCTIONS, YOU GET NO SUPPORT.

Wietse

 there is *nothing* but empty folders - so where does it install to?
 also tried with make install DESTDIR=%{buildroot} -non-interactive
 ___
 
 looks like postfix-install is *not* called with all the makro-params
 
 LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
 shlib_directory=${shlib_directory:-`LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib
  
 bin/postconf -dhx shlib_directory`} /bin/sh postfix-install
 
 *these* are important for the package building process:
 
 -package -non-interactive install_root=%{buildroot} 
 config_directory=%{postfix_config_dir} 
 meta_directory=%{postfix_daemon_dir} 
 daemon_directory=%{postfix_daemon_dir} 
 shlib_directory=%{postfix_shlib_dir} 
 command_directory=%{postfix_command_dir} 
 queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
 sendmail_path=%{postfix_command_dir}/sendmail 
 newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
 mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
 manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
 readme_directory=%{postfix_readme_dir}
 ___
 
 [builduser@testserver:/rpmbuild/SPECS]$ ls -R 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/ 
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/:
 total 12K
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 etc
 drwxr-xr-x 4 builduser builduser 4.0K 2015-02-12 14:26 usr
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 var
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc:
 total 4.0K
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pam.d
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc/pam.d:
 total 4.0K
 -rw-r--r-- 1 builduser builduser 76 2015-02-12 14:26 smtp.postfix
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr:
 total 8.0K
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 lib64
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 share
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64:
 total 4.0K
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 postfix
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64/postfix:
 total 0
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share:
 total 4.0K
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 doc
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc:
 total 4.0K
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 postfix-3.0.0
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0:
 total 4.0K
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 examples
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0/examples:
 total 0
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var:
 total 4.0K
 drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 spool
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool:
 total 4.0K
 drwxr-xr-x 15 builduser builduser 4.0K 2015-02-12 14:26 postfix
 
 /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool/postfix:
 total 52K
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 active
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 bounce
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 corrupt
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 defer
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 deferred
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 flush
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 incoming
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 maildrop
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pid
 drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 

Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 15:32 schrieb Wietse Venema:

Wietse Venema:

li...@rhsoft.net:
[ Charset windows-1252 converted... ]


Am 12.02.2015 um 14:12 schrieb Wietse Venema:

li...@rhsoft.net:

well, set LD_LIBRARY_PATH does the trick
shoudn't postfix-install do that on it's own?


You MUST NOT invoke postfix-install directly.
You MUST use make install as described in the INSTALL instructions


besides that SPEC is derived from Redhat ones years ago using make
install seems to change the whole semantic of what is happening in the
%install section


Instead of sh postfix-install name=value use make install name=value


i did that as you can see on bottom if the message you responded to

make install -non-interactive install_root=%{buildroot} 
config_directory=%{postfix_config_dir} 
meta_directory=%{postfix_daemon_dir} 
daemon_directory=%{postfix_daemon_dir} 
shlib_directory=%{postfix_shlib_dir} 
command_directory=%{postfix_command_dir} 
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
sendmail_path=%{postfix_command_dir}/sendmail 
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
readme_directory=%{postfix_readme_dir} || exit 1


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
  Instead of sh postfix-install name=value use make install name=value
 
 i did that as you can see on bottom if the message you responded to
 
 make install -non-interactive install_root=%{buildroot} 
 config_directory=%{postfix_config_dir} 
 meta_directory=%{postfix_daemon_dir} 
 daemon_directory=%{postfix_daemon_dir} 
 shlib_directory=%{postfix_shlib_dir} 
 command_directory=%{postfix_command_dir} 
 queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
 sendmail_path=%{postfix_command_dir}/sendmail 
 newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
 mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
 manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
 readme_directory=%{postfix_readme_dir} || exit 1

No, I said:

make install name=value

without rpmbuild crap.  I support make install only. I do not support
rcpmbuild crap.

I want you to execute the command without rpmbuild crap, and if
that command without rpmbuild crap does not work, then I will try
to find out why that command without rpmbuild crap does not work.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
Wietse Venema:
 li...@rhsoft.net:
 [ Charset windows-1252 converted... ]
  
  Am 12.02.2015 um 14:12 schrieb Wietse Venema:
   li...@rhsoft.net:
   well, set LD_LIBRARY_PATH does the trick
   shoudn't postfix-install do that on it's own?
  
   You MUST NOT invoke postfix-install directly.
   You MUST use make install as described in the INSTALL instructions
  
  besides that SPEC is derived from Redhat ones years ago using make 
  install seems to change the whole semantic of what is happening in the 
  %install section

Instead of sh postfix-install name=value use make install name=value

Wietse
 The Postfix installation procedure as documented installs Postfix
 without the problems that you keep reporting.
 
 The RELEASE_NOTES say at the top of the file, to avoid massive
 frustration I will not repeat that text here, but summarize
 it as YOU IGNORE INSTRUCTIONS, YOU GET NO SUPPORT.
 
   Wietse
 
  there is *nothing* but empty folders - so where does it install to?
  also tried with make install DESTDIR=%{buildroot} -non-interactive
  ___
  
  looks like postfix-install is *not* called with all the makro-params
  
  LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
  shlib_directory=${shlib_directory:-`LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib
   
  bin/postconf -dhx shlib_directory`} /bin/sh postfix-install
  
  *these* are important for the package building process:
  
  -package -non-interactive install_root=%{buildroot} 
  config_directory=%{postfix_config_dir} 
  meta_directory=%{postfix_daemon_dir} 
  daemon_directory=%{postfix_daemon_dir} 
  shlib_directory=%{postfix_shlib_dir} 
  command_directory=%{postfix_command_dir} 
  queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
  sendmail_path=%{postfix_command_dir}/sendmail 
  newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
  mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
  manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
  readme_directory=%{postfix_readme_dir}
  ___
  
  [builduser@testserver:/rpmbuild/SPECS]$ ls -R 
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/ 
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/:
  total 12K
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 etc
  drwxr-xr-x 4 builduser builduser 4.0K 2015-02-12 14:26 usr
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 var
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc:
  total 4.0K
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pam.d
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc/pam.d:
  total 4.0K
  -rw-r--r-- 1 builduser builduser 76 2015-02-12 14:26 smtp.postfix
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr:
  total 8.0K
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 lib64
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 share
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64:
  total 4.0K
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 postfix
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64/postfix:
  total 0
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share:
  total 4.0K
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 doc
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc:
  total 4.0K
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 postfix-3.0.0
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0:
  total 4.0K
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 examples
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0/examples:
  total 0
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var:
  total 4.0K
  drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 spool
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool:
  total 4.0K
  drwxr-xr-x 15 builduser builduser 4.0K 2015-02-12 14:26 postfix
  
  /home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool/postfix:
  total 52K
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 active
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 bounce
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 corrupt
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 defer
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 deferred
  drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 flush
  drwxr-xr-x 2 builduser builduser 4.0K 

Re: rpmbuild and shared=yes

2015-02-12 Thread Andrew Ho
This is the tricks for rpmbuild. postconf relies on 
%{postfix_lib_dir}libpostfix-global.so for postfix-install.


- - postfix.spec --
mkdir -p $RPM_BUILD_ROOT%{postfix_lib_dir}

if [ ! -f %{postfix_lib_dir}/libpostfix-global.so ] ; then
mkdir -p %{postfix_lib_dir}
install lib/libpostfix-global.so %{postfix_lib_dir}
install lib/libpostfix-util.so  %{postfix_lib_dir}
fi


sh postfix-install -non-interactive \
   install_root=$RPM_BUILD_ROOT \
   config_directory=%{postfix_config_dir} \
   daemon_directory=%{postfix_daemon_dir} \
   command_directory=%{postfix_command_dir} \
   queue_directory=%{postfix_queue_dir} \
   data_directory=%{postfix_data_dir} \
   sendmail_path=%{postfix_command_dir}/sendmail.postfix \
   newaliases_path=%{_bindir}/newaliases.postfix \
   mailq_path=%{_bindir}/mailq.postfix \
   mail_owner=%{postfix_user} \
   setgid_group=%{maildrop_group} \
   manpage_directory=%{_mandir} \
   meta_directory=%{postfix_daemon_dir} \
   sample_directory=%{postfix_sample_dir} \
   readme_directory=%{postfix_readme_dir} \
   shlib_directory=%{postfix_lib_dir} \
|| exit 1

---end --

Have fun.

On 02/12/2015 09:32 AM, Wietse Venema wrote:

Wietse Venema:

li...@rhsoft.net:
[ Charset windows-1252 converted... ]

Am 12.02.2015 um 14:12 schrieb Wietse Venema:

li...@rhsoft.net:

well, set LD_LIBRARY_PATH does the trick
shoudn't postfix-install do that on it's own?

You MUST NOT invoke postfix-install directly.
You MUST use make install as described in the INSTALL instructions

besides that SPEC is derived from Redhat ones years ago using make
install seems to change the whole semantic of what is happening in the
%install section

Instead of sh postfix-install name=value use make install name=value

Wietse

The Postfix installation procedure as documented installs Postfix
without the problems that you keep reporting.

The RELEASE_NOTES say at the top of the file, to avoid massive
frustration I will not repeat that text here, but summarize
it as YOU IGNORE INSTRUCTIONS, YOU GET NO SUPPORT.

Wietse


there is *nothing* but empty folders - so where does it install to?
also tried with make install DESTDIR=%{buildroot} -non-interactive
___

looks like postfix-install is *not* called with all the makro-params

LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib
shlib_directory=${shlib_directory:-`LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib
bin/postconf -dhx shlib_directory`} /bin/sh postfix-install

*these* are important for the package building process:

-package -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir}
shlib_directory=%{postfix_shlib_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir}
___

[builduser@testserver:/rpmbuild/SPECS]$ ls -R
/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/:
total 12K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 etc
drwxr-xr-x 4 builduser builduser 4.0K 2015-02-12 14:26 usr
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 var

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc:
total 4.0K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pam.d

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc/pam.d:
total 4.0K
-rw-r--r-- 1 builduser builduser 76 2015-02-12 14:26 smtp.postfix

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr:
total 8.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 lib64
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 share

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64:
total 4.0K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 postfix

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64/postfix:
total 0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share:
total 4.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 doc

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc:
total 4.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 postfix-3.0.0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0:
total 4.0K
drwxr-xr-x 

Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 14:12 schrieb Wietse Venema:

li...@rhsoft.net:

well, set LD_LIBRARY_PATH does the trick
shoudn't postfix-install do that on it's own?


You MUST NOT invoke postfix-install directly.
You MUST use make install as described in the INSTALL instructions


besides that SPEC is derived from Redhat ones years ago using make 
install seems to change the whole semantic of what is happening in the 
%install section


there is *nothing* but empty folders - so where does it install to?
also tried with make install DESTDIR=%{buildroot} -non-interactive
___

looks like postfix-install is *not* called with all the makro-params

LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
shlib_directory=${shlib_directory:-`LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
bin/postconf -dhx shlib_directory`} /bin/sh postfix-install


*these* are important for the package building process:

-package -non-interactive install_root=%{buildroot} 
config_directory=%{postfix_config_dir} 
meta_directory=%{postfix_daemon_dir} 
daemon_directory=%{postfix_daemon_dir} 
shlib_directory=%{postfix_shlib_dir} 
command_directory=%{postfix_command_dir} 
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
sendmail_path=%{postfix_command_dir}/sendmail 
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
readme_directory=%{postfix_readme_dir}

___

[builduser@testserver:/rpmbuild/SPECS]$ ls -R 
/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/ 


/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/:
total 12K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 etc
drwxr-xr-x 4 builduser builduser 4.0K 2015-02-12 14:26 usr
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 var

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc:
total 4.0K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pam.d

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/etc/pam.d:
total 4.0K
-rw-r--r-- 1 builduser builduser 76 2015-02-12 14:26 smtp.postfix

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr:
total 8.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 lib64
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 share

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64:
total 4.0K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 postfix

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/lib64/postfix:
total 0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share:
total 4.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 doc

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc:
total 4.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 postfix-3.0.0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0:
total 4.0K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 examples

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/usr/share/doc/postfix-3.0.0/examples:
total 0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var:
total 4.0K
drwxr-xr-x 3 builduser builduser 4.0K 2015-02-12 14:26 spool

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool:
total 4.0K
drwxr-xr-x 15 builduser builduser 4.0K 2015-02-12 14:26 postfix

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool/postfix:
total 52K
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 active
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 bounce
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 corrupt
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 defer
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 deferred
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 flush
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 incoming
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 maildrop
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 pid
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 private
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 public
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 saved
drwxr-xr-x 2 builduser builduser 4.0K 2015-02-12 14:26 trace

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool/postfix/active:
total 0

/home/builduser/rpmbuild/BUILDROOT/postfix-3.0.0-4.fc21.20150212.rh.x86_64/var/spool/postfix/bounce:
total 0


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
 well, set LD_LIBRARY_PATH does the trick
 shoudn't postfix-install do that on it's own?

You MUST NOT invoke postfix-install directly.

You MUST use make install as described in the INSTALL instructions.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
 Am 12.02.2015 um 17:08 schrieb Wietse Venema:
  li...@rhsoft.net:
  according to the subject a You MUST use make non-interactive-package
  would have saved a lot of noise including the completly unnecessary
  flames about rpm crap without *by all respect* no clue about how it
  works and that the macros are replaced before any bit of postfix source
  could face them
 
  I provide the interfaces. It is your job to choose the right one.
 
 not when you say You MUST use THAT because if i try to mangle that 
 because it just don't work you would repsond did i say this and that?

Without a clear statement what you want (build installable package)
I have to guess that you want to install Postfix. The supported
interface is make whatever. People who grope under that interface
are lucky if I provide any support at all.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net



Am 12.02.2015 um 17:13 schrieb Viktor Dukhovni:

On Thu, Feb 12, 2015 at 04:58:39PM +0100, li...@rhsoft.net wrote:

that below works like a charm:

make non-interactive-package install_root=%{buildroot}
config_directory=%{postfix_config_dir} meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir} shlib_directory=%{postfix_shlib_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1


After this installs the bits Postfix always installs (that are
listed in the stock postfix-files):

 * If you're building with dynamicmaps=yes and want to create
   separate packages for the various database drivers, then
   consider creating a per-driver .cf file in:

  $meta_directory/dynamicmaps.cf.d/

   listing just that table type and corresponding module path.

   plus whatever logic you'll need to deliver the plugin module
   and the corresponding dynamicmaps config snippet as a separate
   package.

 * If you want to install optional test bits:

posttls-finger, smtp-sink, smtp-source, ...

   You'll have to copy those in yourself, and add them to postfix-files
   or postfix-files.d/sub-package as appropriate


thanks for the hint, only everywhere used libraries are linked

the reason for shared=yes was more to get the single postfix binaries 
smaller and using shared libraries for optimized memory usage


well, the manpages are already in a subpackage only installed on the 
admin-machine instead everywhere


%files manpages
%{postfix_doc_dir}
%attr(0644, root, root) %{_mandir}/man1/*
%attr(0644, root, root) %{_mandir}/man5/*
%attr(0644, root, root) %{_mandir}/man8/*


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 17:18 schrieb Wietse Venema:

li...@rhsoft.net:

Am 12.02.2015 um 17:08 schrieb Wietse Venema:

li...@rhsoft.net:

according to the subject a You MUST use make non-interactive-package
would have saved a lot of noise including the completly unnecessary
flames about rpm crap without *by all respect* no clue about how it
works and that the macros are replaced before any bit of postfix source
could face them


I provide the interfaces. It is your job to choose the right one.


not when you say You MUST use THAT because if i try to mangle that
because it just don't work you would repsond did i say this and that?


Without a clear statement what you want (build installable package)
I have to guess that you want to install Postfix. The supported
interface is make whatever. People who grope under that interface
are lucky if I provide any support at all.


can we stop that discussion and both admit that we handeled the issue 
not really good? Without a clear statement what you want when the 
subject begins with rpmbuild? seriously? :-)




Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 15:50 schrieb Wietse Venema:

li...@rhsoft.net:

Instead of sh postfix-install name=value use make install name=value


i did that as you can see on bottom if the message you responded to

make install -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir}
shlib_directory=%{postfix_shlib_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1


No, I said:

make install name=value

without rpmbuild crap.  I support make install only. I do not support
rcpmbuild crap.


interesting attitude in context of subject rpmbuild and shared=yes


I want you to execute the command without rpmbuild crap, and if
that command without rpmbuild crap does not work, then I will try
to find out why that command without rpmbuild crap does not work.


%{whatever} is replaced by the makros defined on top of the SPEC to 
write paths just once and re-use them, they are simply replaced


frankly for any other package you use make install 
DESTDIR=%{buildroot} which installs the already compiled binaries in 
buildroot and that's it, the paths are defined by ./configure


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
  No, I said:
 
  make install name=value
 
  without rpmbuild crap.  I support make install only. I do not support
  rcpmbuild crap.
 
 interesting attitude in context of subject rpmbuild and shared=yes

Please stick to the supported interfaces:

make makefiles name=value...
make
make install name=value...
make upgrade name=value...
etcetera

Where is your make command without rpmbuild crap? I am willing
to provide support at that level. I do not provide support at the
level of RedHat, Debian, Solaris, *BSD, or Apple package managers.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net
the most likely reason is make install versus make upgrade which 
*both* don't apply for a rpmbuild because there is no business for 
interactive and no business for non-interactive version, for upgrades


would make install just work non-interactive problem gone

# make install   (interactive version, first time install)
# make upgrade   (non-interactive version, for upgrades)

pretty sure the reason why Redhat is using postfix-install while for 
all other packages make install DESTDIR=%{buildroot} is in use


Am 12.02.2015 um 16:00 schrieb li...@rhsoft.net:

Am 12.02.2015 um 15:50 schrieb Wietse Venema:

li...@rhsoft.net:

Instead of sh postfix-install name=value use make install
name=value


i did that as you can see on bottom if the message you responded to

make install -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir}
shlib_directory=%{postfix_shlib_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1


No, I said:

make install name=value

without rpmbuild crap.  I support make install only. I do not support
rcpmbuild crap.


interesting attitude in context of subject rpmbuild and shared=yes


I want you to execute the command without rpmbuild crap, and if
that command without rpmbuild crap does not work, then I will try
to find out why that command without rpmbuild crap does not work.


%{whatever} is replaced by the makros defined on top of the SPEC to
write paths just once and re-use them, they are simply replaced

frankly for any other package you use make install
DESTDIR=%{buildroot} which installs the already compiled binaries in
buildroot and that's it, the paths are defined by ./configure


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 16:10 schrieb Wietse Venema:

li...@rhsoft.net:

No, I said:

make install name=value

without rpmbuild crap.  I support make install only. I do not support
rcpmbuild crap.


interesting attitude in context of subject rpmbuild and shared=yes


Please stick to the supported interfaces:

make makefiles name=value...
make
make install name=value...
make upgrade name=value...
etcetera

Where is your make command without rpmbuild crap? I am willing
to provide support at that level. I do not provide support at the
level of RedHat, Debian, Solaris, *BSD, or Apple package managers


the *real problem* is that make install is *interactive* and the 
non-interactive make upgrade can't work at all while make install 
-non-interactive talks about nothing to do for update


config_directory=%{postfix_config_dir} is *notging else* than 
config_directory=/etc/postfix and i replaced *long before* make 
install will be called


the whole purpose of a rpmbuild is to install into an *always empty* 
tree as ordinary user and after that pack that tree with all folders, 
files and permissions into an archive





Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
Andrew Ho:
 sh postfix-install -non-interactive \

THIS IS NOT SUPPORTED. USE MAKE INSTALL.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
 the most likely reason is make install versus make upgrade which 
 *both* don't apply for a rpmbuild because there is no business for 
 interactive and no business for non-interactive version, for upgrades
 
 would make install just work non-interactive problem gone
 
 # make install   (interactive version, first time install)
 # make upgrade   (non-interactive version, for upgrades)

The only difference between install and upgrade is that one is
interactive and the other is not. That is, install is an upgrade
from zero with all the answers pre-determined.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net

Am 12.02.2015 um 16:21 schrieb Wietse Venema:

li...@rhsoft.net:

the most likely reason is make install versus make upgrade which
*both* don't apply for a rpmbuild because there is no business for
interactive and no business for non-interactive version, for upgrades

would make install just work non-interactive problem gone

# make install   (interactive version, first time install)
# make upgrade   (non-interactive version, for upgrades)


The only difference between install and upgrade is that one is
interactive and the other is not. That is, install is an upgrade
from zero with all the answers pre-determined


make install -non-interactive simply ends in *nothing* installed into 
the build-tree nor somewhere else


make: Nothing to be done for 'update'.
[src/fsstone]
make: Nothing to be done for 'update'.
[src/smtpstone]
make: Nothing to be done for 'update'.
[src/sendmail]
make: Nothing to be done for 'update'.
[src/error]
make: Nothing to be done for 'update'.
[src/pickup]
make: Nothing to be done for 'update'.
[src/cleanup]
make: Nothing to be done for 'update'.
[src/smtpd]
make: Nothing to be done for 'update'.
[src/local]
make: Nothing to be done for 'update'.
[src/trivial-rewrite]
make: Nothing to be done for 'update'.
[src/qmgr]
make: Nothing to be done for 'update'.
[src/oqmgr]
make: Nothing to be done for 'update'.
[src/smtp]
make: Nothing to be done for 'update'.
[src/bounce]
make: Nothing to be done for 'update'.
[src/pipe]
make: Nothing to be done for 'update'.
[src/showq]
make: Nothing to be done for 'update'.
[src/postalias]
make: Nothing to be done for 'update'.
[src/postcat]
make: Nothing to be done for 'update'.
[src/postconf]
make: Nothing to be done for 'update'.
[src/postdrop]
make: Nothing to be done for 'update'.
[src/postkick]
make: Nothing to be done for 'update'.
[src/postlock]
make: Nothing to be done for 'update'.
[src/postlog]
make: Nothing to be done for 'update'.
[src/postmap]
make: Nothing to be done for 'update'.
[src/postqueue]
make: Nothing to be done for 'update'.
[src/postsuper]
make: Nothing to be done for 'update'.
[src/qmqpd]
make: Nothing to be done for 'update'.
[src/spawn]
make: Nothing to be done for 'update'.
[src/flush]
make: Nothing to be done for 'update'.
[src/verify]
make: Nothing to be done for 'update'.
[src/virtual]
make: Nothing to be done for 'update'.
[src/proxymap]
make: Nothing to be done for 'update'.
[src/anvil]
make: Nothing to be done for 'update'.
[src/scache]
make: Nothing to be done for 'update'.
[src/discard]
make: Nothing to be done for 'update'.
[src/tlsmgr]
make: Nothing to be done for 'update'.
[src/postmulti]
make: Nothing to be done for 'update'.
[src/postscreen]
make: Nothing to be done for 'update'.
[src/dnsblog]
make: Nothing to be done for 'update'.
[src/tlsproxy]
make: Nothing to be done for 'update'.
[src/posttls-finger]
make: Nothing to be done for 'update'.
LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
shlib_directory=${shlib_directory:-`LD_LIBRARY_PATH=/home/builduser/rpmbuild/BUILD/postfix-3.0.0/lib 
bin/postconf -dhx shlib_directory`} /bin/sh \

postfix-install


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
[ Charset windows-1252 converted... ]
 Am 12.02.2015 um 16:21 schrieb Wietse Venema:
  li...@rhsoft.net:
  the most likely reason is make install versus make upgrade which
  *both* don't apply for a rpmbuild because there is no business for
  interactive and no business for non-interactive version, for upgrades
 
  would make install just work non-interactive problem gone
 
  # make install   (interactive version, first time install)
  # make upgrade   (non-interactive version, for upgrades)
 
  The only difference between install and upgrade is that one is
  interactive and the other is not. That is, install is an upgrade
  from zero with all the answers pre-determined
 
 make install -non-interactive simply ends in *nothing* installed into 
 the build-tree nor somewhere else

Where did I tell you to make install -non-interactive?
  
As I explained above, use make upgrade you want a non-interactive
install.

Therefore:

make upgrade name=value ...

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread Viktor Dukhovni
On Thu, Feb 12, 2015 at 04:29:37PM +0100, li...@rhsoft.net wrote:

 The only difference between install and upgrade is that one is
 interactive and the other is not. That is, install is an upgrade
 from zero with all the answers pre-determined
 
 make install -non-interactive simply ends in *nothing* installed into the
 build-tree nor somewhere else

The -non-interactive option is postfix-install command-line argument, it
is NOT a make argument.  The Postfix Makefile contains the following relevant
targets:

install: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install

package: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -package

upgrade: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -non-interactive


non-interactive-package: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -non-interactive -package

For non-interactive building of packages use:

http://www.postfix.org/PACKAGE_README.html

If you want to fully automate this process, specify all
the non-default installation parameters on the command
line:

 % make non-interactive-package install_root=/some/where...

With Postfix versions before 2.2 you must invoke the
post-install script directly (% sh post-install -non-interactive
install_root...).

With Postfix 3.0 and later, the command make package
name=value
... will replace the string MAIL_VERSION in a configuration
parameter value with the Postfix release version. Do not
try to specify something like $mail_version on this command
line. This produces inconsistent results with different
versions of the make(1) command.

This was even updated for 3.0.

-- 
Viktor.


Re: rpmbuild and shared=yes

2015-02-12 Thread Viktor Dukhovni
On Thu, Feb 12, 2015 at 10:40:47AM -0500, Wietse Venema wrote:

 Where did I tell you to make install -non-interactive?
   
 As I explained above, use make upgrade you want a non-interactive
 install.

I believe he does not want an install (directly to the final
locations), he wants a package build, therefore as per my other
email.

-- 
Viktor.


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 16:43 schrieb Viktor Dukhovni:

On Thu, Feb 12, 2015 at 10:40:47AM -0500, Wietse Venema wrote:


Where did I tell you to make install -non-interactive?
   
As I explained above, use make upgrade you want a non-interactive
install.


I believe he does not want an install (directly to the final
locations), he wants a package build, therefore as per my other
email


thank you!

according to the subject a You MUST use make non-interactive-package 
would have saved a lot of noise including the completly unnecessary 
flames about rpm crap without *by all respect* no clue about how it 
works and that the macros are replaced before any bit of postfix source 
could face them



that below works like a charm:

make non-interactive-package install_root=%{buildroot} 
config_directory=%{postfix_config_dir} 
meta_directory=%{postfix_daemon_dir} 
daemon_directory=%{postfix_daemon_dir} 
shlib_directory=%{postfix_shlib_dir} 
command_directory=%{postfix_command_dir} 
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir} 
sendmail_path=%{postfix_command_dir}/sendmail 
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq 
mail_owner=%{postfix_user} setgid_group=%{maildrop_group} 
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir} 
readme_directory=%{postfix_readme_dir} || exit 1



now it's also clear from where the postfix-install call is coming and 
since it worked for many years and also 3.0 without shared, well..


With Postfix versions before 2.2 you must invoke the post-install script 
directly (% sh post-install -non-interactive install_root...)


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 17:01 schrieb Wietse Venema:

Viktor Dukhovni:

On Thu, Feb 12, 2015 at 10:40:47AM -0500, Wietse Venema wrote:


Where did I tell you to make install -non-interactive?
   
As I explained above, use make upgrade you want a non-interactive
install.


I believe he does not want an install (directly to the final
locations), he wants a package build, therefore as per my other
email.


And this is supported as well. I can provide the necessary interfaces
(lead the horse to the water) but I can't force people to use them
(drink the water)


that is all true - but you could give the correct answer or none when 
somebody posts the *working* solution he found out by himself instead a 
wrong one with a big fat You MUST use - your repsone below was wrong 
and leaded to all the other try around and ping pong


frankly *i had the build running* and so answered my own question with 
the intention others with the same problems can find that information 
later and got corrected with non working instructions


that is not helpful

 Weitergeleitete Nachricht 
Betreff: Re: rpmbuild and shared=yes
Datum: Thu, 12 Feb 2015 08:12:44 -0500 (EST)
Von: Wietse Venema wie...@porcupine.org
An: li...@rhsoft.net li...@rhsoft.net
Kopie (CC): postfix-users@postfix.org

li...@rhsoft.net:
 well, set LD_LIBRARY_PATH does the trick
 shoudn't postfix-install do that on it's own?

You MUST NOT invoke postfix-install directly.
You MUST use make install as described in the INSTALL instructions.



Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
Viktor Dukhovni:
 On Thu, Feb 12, 2015 at 10:40:47AM -0500, Wietse Venema wrote:
 
  Where did I tell you to make install -non-interactive?

  As I explained above, use make upgrade you want a non-interactive
  install.
 
 I believe he does not want an install (directly to the final
 locations), he wants a package build, therefore as per my other
 email.

And this is supported as well. I can provide the necessary interfaces
(lead the horse to the water) but I can't force people to use them
(drink the water).

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
 according to the subject a You MUST use make non-interactive-package 
 would have saved a lot of noise including the completly unnecessary 
 flames about rpm crap without *by all respect* no clue about how it 
 works and that the macros are replaced before any bit of postfix source 
 could face them

I provide the interfaces. It is your job to choose the right one.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net



Am 12.02.2015 um 17:08 schrieb Wietse Venema:

li...@rhsoft.net:

according to the subject a You MUST use make non-interactive-package
would have saved a lot of noise including the completly unnecessary
flames about rpm crap without *by all respect* no clue about how it
works and that the macros are replaced before any bit of postfix source
could face them


I provide the interfaces. It is your job to choose the right one.


not when you say You MUST use THAT because if i try to mangle that 
because it just don't work you would repsond did i say this and that?


Re: rpmbuild and shared=yes

2015-02-12 Thread Viktor Dukhovni
On Thu, Feb 12, 2015 at 04:58:39PM +0100, li...@rhsoft.net wrote:

 that below works like a charm:
 
 make non-interactive-package install_root=%{buildroot}
 config_directory=%{postfix_config_dir} meta_directory=%{postfix_daemon_dir}
 daemon_directory=%{postfix_daemon_dir} shlib_directory=%{postfix_shlib_dir}
 command_directory=%{postfix_command_dir}
 queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
 sendmail_path=%{postfix_command_dir}/sendmail
 newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
 mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
 manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
 readme_directory=%{postfix_readme_dir} || exit 1

After this installs the bits Postfix always installs (that are
listed in the stock postfix-files):

* If you're building with dynamicmaps=yes and want to create
  separate packages for the various database drivers, then
  consider creating a per-driver .cf file in:

  $meta_directory/dynamicmaps.cf.d/

  listing just that table type and corresponding module path.

  plus whatever logic you'll need to deliver the plugin module
  and the corresponding dynamicmaps config snippet as a separate
  package.

* If you want to install optional test bits:

posttls-finger, smtp-sink, smtp-source, ...

  You'll have to copy those in yourself, and add them to postfix-files
  or postfix-files.d/sub-package as appropriate.

-- 
Viktor.


Re: rpmbuild and shared=yes

2015-02-12 Thread Wietse Venema
li...@rhsoft.net:
 Am 12.02.2015 um 17:18 schrieb Wietse Venema:
  li...@rhsoft.net:
  Am 12.02.2015 um 17:08 schrieb Wietse Venema:
  li...@rhsoft.net:
  according to the subject a You MUST use make non-interactive-package
  would have saved a lot of noise including the completly unnecessary
  flames about rpm crap without *by all respect* no clue about how it
  works and that the macros are replaced before any bit of postfix source
  could face them
 
  I provide the interfaces. It is your job to choose the right one.
 
  not when you say You MUST use THAT because if i try to mangle that
  because it just don't work you would repsond did i say this and that?
 
  Without a clear statement what you want (build installable package)
  I have to guess that you want to install Postfix. The supported
  interface is make whatever. People who grope under that interface
  are lucky if I provide any support at all.
 
 can we stop that discussion and both admit that we handeled the issue 
 not really good? Without a clear statement what you want when the 
 subject begins with rpmbuild? seriously? :-)

You are like people who ask I use Sendmail or qmail or Exim feature
X, how do I do that with Postfix?, without a clear statement of
what X does. I am not interested in how rpmbuild works.

Wietse


Re: rpmbuild and shared=yes

2015-02-12 Thread li...@rhsoft.net


Am 12.02.2015 um 17:33 schrieb Wietse Venema:

li...@rhsoft.net:

Am 12.02.2015 um 17:18 schrieb Wietse Venema:

li...@rhsoft.net:

Am 12.02.2015 um 17:08 schrieb Wietse Venema:

li...@rhsoft.net:

according to the subject a You MUST use make non-interactive-package
would have saved a lot of noise including the completly unnecessary
flames about rpm crap without *by all respect* no clue about how it
works and that the macros are replaced before any bit of postfix source
could face them


I provide the interfaces. It is your job to choose the right one.


not when you say You MUST use THAT because if i try to mangle that
because it just don't work you would repsond did i say this and that?


Without a clear statement what you want (build installable package)
I have to guess that you want to install Postfix. The supported
interface is make whatever. People who grope under that interface
are lucky if I provide any support at all.


can we stop that discussion and both admit that we handeled the issue
not really good? Without a clear statement what you want when the
subject begins with rpmbuild? seriously? :-)


You are like people who ask I use Sendmail or qmail or Exim feature
X, how do I do that with Postfix?, without a clear statement of
what X does. I am not interested in how rpmbuild works.


well, you are not able to admit a mistake, so be it

Without a clear statement what you want (build installable package) is 
ridiculous because rpmbuild is an as clear as possible statement that 
the goal is build installable package as well you do not need to be 
interested in how rpmbuild works


but than you should not insist in remove the crap of macros while the 
person on the other side is knowing how it works and that there is no 
technical differene between something=/path/ or something=%{path_macro} 
besides you have to type that only once on top, reuse it in the rest of 
the file and if you change a value it's consistent everywhere