Am 06.03.2017 um 14:56 schrieb Bart Coninckx via samba:>>> missed that - but must be the case because he refers to RHEL7/CentOS7 >>> which ships with 4.4.4 and not 4.1.x - anyways, the tree brelow the >>> install prefix is the same and the main part of the coniguration >>> lives below the lib folder whereever it is located and so the point >>> was just remove the configs itself won't reset completly > >> You, being (by the sound of it) a Red-Hat user, will very well know >> that you cannot create an AD DC with Red-Hat packages yet, so, unless >> you configure it differently, Samba puts everything into >> /usr/local/samba > > Personally I find it an advantage of Samba living in /usr/local as it emphasizes that this Samba install is not created from packages and it represents it's own biotope because all relevant folders are in that one folder.well, there is nothing different when you use rpmbuild and chose the prefix you want besides that: * cleanup of orphan files * simpe upgarde/downgrade because you have your prebuild .rpm files * no need of devel-packages / compilers on the target machine * no need to --exclude=/usr/local/smaba/var/lib/samba fpr rsync if you build on a different machine because rpm don't touch files which it didn't create * easy re-use on serveral machines including a testing-one the only real difference is that "make install" goes into the buildfolder - i don't see any advantage in "as it emphasizes that this Samba install is not created from packages" since for a decade now i override postfix, mysql, httpd, apr, php and so on on Fedora with self built packages and a higher epoch in the rpm-spec so that the own repos win
-----Original message----- From:Reindl Harald via samba <samba at lists.samba.org> Sent:Mon 06-03-2017 15:50 Subject:Re: [Samba] Missing security tab samba 4.1.13 To:samba at lists.samba.org;>well, there is nothing different when you use rpmbuild and chose the >prefix you want besides that: > >* cleanup of orphan files >* simpe upgarde/downgrade because you have your prebuild .rpm files >* no need of devel-packages / compilers on the target machine >* no need to --exclude=/usr/local/smaba/var/lib/samba fpr rsync > if you build on a different machine because rpm don't touch > files which it didn't create >* easy re-use on serveral machines including a testing-one > >the only real difference is that "make install" goes into the >buildfolder - i don't see any advantage in "as it emphasizes that this >Samba install is not created from packages" since for a decade now i >override postfix, mysql, httpd, apr, php and so on on Fedora with self >built packages and a higher epoch in the rpm-spec so that the own repos winFrankly, I have never done that before. I did not find a wiki entry for that and I have somewhat of a time constraint, but might check that out later, BC
On Mon, 6 Mar 2017 15:48:32 +0100 Reindl Harald via samba <samba at lists.samba.org> wrote:> well, there is nothing different when you use rpmbuild and chose the > prefix you want besides that: > > * cleanup of orphan files > * simpe upgarde/downgrade because you have your prebuild .rpm files > * no need of devel-packages / compilers on the target machine > * no need to --exclude=/usr/local/smaba/var/lib/samba fpr rsync > if you build on a different machine because rpm don't touch > files which it didn't create > * easy re-use on serveral machines including a testing-one > > the only real difference is that "make install" goes into the > buildfolder - i don't see any advantage in "as it emphasizes that > this Samba install is not created from packages" since for a decade > now i override postfix, mysql, httpd, apr, php and so on on Fedora > with self built packages and a higher epoch in the rpm-spec so that > the own repos win >OK, you sound like you know how to do this, so why don't you add it to the Samba wiki, or if you don't want to register on the wiki, just write it all down, send it to me and I will put it on the wiki for you. Rowland
Am 06.03.2017 um 16:06 schrieb Rowland Penny:> On Mon, 6 Mar 2017 15:48:32 +0100 > Reindl Harald via samba <samba at lists.samba.org> wrote: > >> well, there is nothing different when you use rpmbuild and chose the >> prefix you want besides that: >> >> * cleanup of orphan files >> * simpe upgarde/downgrade because you have your prebuild .rpm files >> * no need of devel-packages / compilers on the target machine >> * no need to --exclude=/usr/local/smaba/var/lib/samba fpr rsync >> if you build on a different machine because rpm don't touch >> files which it didn't create >> * easy re-use on serveral machines including a testing-one >> >> the only real difference is that "make install" goes into the >> buildfolder - i don't see any advantage in "as it emphasizes that >> this Samba install is not created from packages" since for a decade >> now i override postfix, mysql, httpd, apr, php and so on on Fedora >> with self built packages and a higher epoch in the rpm-spec so that >> the own repos win > > OK, you sound like you know how to do this, so why don't you add it to > the Samba wiki, or if you don't want to register on the wiki, just > write it all down, send it to me and I will put it on the wiki for youin short: it's not samba specific at all https://wiki.centos.org/HowTos/SetupRpmBuildEnvironment you just place the same configure line with whatever otpions in the specfile as well as any other stuff and scriptings, just keep the %files the first time empty and then you get every folder or file listed at the error output which is not packaged and just write your filelist as start in doubt just use a already existing spec file which for sure exists and modify it for your needs ___________________________________________________ just a simple one - no rocket science [builduser at testserver:/rpmbuild/SPECS]$ cat /rpmbuild/SPECS/aespipe.spec Summary: AES-encryption tool for tar/cpio and loop-aes images Name: aespipe Version: 2.4d Release: 2%{?dist} License: GPL Group: Applications URL: http://loop-aes.sourceforge.net/ Source0: %{name}/%{name}-v%{version}.tar.bz2 BuildRequires: autoconf BuildRequires: automake %description aespipe is an encryption tool that reads from standard input and writes to standard output. It uses the AES (Rijndael) cipher It can be used as an encryption filter, to create and restore encrypted tar/cpio backup archives and to read/write and convert loop-AES compatible encrypted images %prep %setup -q -n %{name}-v%{version} %build aclocal && autoconf || exit 1 export CFLAGS="%{optflags} -fPIE -fuse-ld=gold -fuse-linker-plugin" export CXXFLAGS="$CFLAGS" export FFLAGS="$CFLAGS" export CPPFLAGS="$CFLAGS" export CC="gcc $CFLAGS" export LDFLAGS="-Wl,-z,now -Wl,-z,relro -Wl,-z,noexecstack -pie $CFLAGS" %configure --enable-intelaes --disable-padlock %{__make} %{?_smp_mflags} amd64 %install install -d %{buildroot}{%{_bindir},%{_mandir}/man1} install %{name} %{buildroot}%{_bindir} install %{name}.1 %{buildroot}%{_mandir}/man1 strip -s %{buildroot}%{_bindir}/%{name} %files %attr(755,root,root) %{_bindir}/* %{_mandir}/man1/* %changelog * Sun May 24 2015 Reindl Harald <h.reindl at thelounge.net> - Update to 2.4d