You are right, I think I will give it a try. So I guess that I will have
to prepare two packages (at least) if I wanna run it on a chroot env.
bind and bind-chrootenv packages.
And I think I should get the specs files from the 9.9.6P1 available on
the SLES12 Repos.
Thanks a lot!
On 19/02/16 12:56, Reindl Harald wrote:
Am 19.02.2016 um 12:46 schrieb Josep Manel Andrés:
I am not too confident to build RPM packages, that is why I wanted to go
for a normal installation from source.
well, learn it, it's really not hard to do
i learnt it the hard way that "make install" over years leaves more and
more mess while a rpm package automatically removes obsolete files and
the build process finally makes sure that it aborts if anything in the
%files section did not exist after compile or a new file is not listed
in %files due a upgrade
you will notice that when you did a major upgrade which don't work and
have no simple downgrade way
_____________________________________
additionally normally on a production server you should not install
compilers and devel-packages and on the other hand on the build machine
install the service with a test config - so you can make sure it will
work on the procution machine or find out what needs to be chnaged
*before* your service fails
you know if your systemd-unit works as expected before it touchs your
server by proper testing and the resulting package pulls all
dependencies on the target machine (at least on Fedora they are
automatically added)
_____________________________________
security: if something goes wrong in the build or with "make install" on
the production machine you have no way to roll back, "make install" with
rpmbuild runs as tesricted user and can't overwrite any files by accident
in short: "make && make install" on production servers is a nogo
On 19/02/16 12:28, Reindl Harald wrote:
Am 19.02.2016 um 12:25 schrieb Reindl Harald:
Am 19.02.2016 um 12:13 schrieb Josep Manel Andrés:
Hi Harald,
Thanks, but I suspect those are the files that come with the default
system installation, but not usable (without modifications) if I have
compiled it from source. Am I right?
well, it should not be that hard to adopt them for your needs or even
build a proper package containing all that stuff - only over my dead
body i would do a "make install" on any machine oustide rpmbuild
BTW - why don't you just take the SuSE src.rpm, modify the SPEC file for
the location where you want to have your own build installed and fire
some sed-commands in the buildprocess to scripts and config files?
that way you only need to swap the tarball, change the version number in
the SPEC and have proper updates in the future
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Josep Manel Andrés (josep.and...@bsc.es)
Operations - Barcelona Supercomputing Center
C/ Jordi Girona, 31 http://www.bsc.es
08034 Barcelona, Spain Tel: +34-93-405 42 14
e-mail: syst...@bsc.es Fax: +34-93-413 77 21
-----------------------------------------------
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
