Joseph L. Brunner
2015-Mar-11 11:52 UTC
[CentOS] SquidAnalyzer: minor trouble building RPM
Thanks for the info. Any reason you're leaving slackware now? -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Niki Kovacs Sent: Wednesday, March 11, 2015 05:23 AM To: centos at centos.org Subject: Re: [CentOS] SquidAnalyzer: minor trouble building RPM Le 11/03/2015 09:40, Niki Kovacs a ?crit :> Unfortunately when I insert the correct version in the spec file, I > get > this: > > $ rpmbuild -ba --clean squidanalyzer.spec > error: line 5: Illegal char '-' in: Version: 6.2-1I'll answer that myself, since I just found the culprit. There's a version mismatch between the tarball and the extracted source directory. Simply renaming the tarball to version 6.2 fixed it. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos
Le 11/03/2015 12:52, Joseph L. Brunner a ?crit :> Thanks for the info. > > Any reason you're leaving slackware now?Yes. As much as I appreciate Slackware's bone-headed philosophy, the installer, the simple startup scripts, the general Keep-It-Simple approach and the overall robustness, the absence of PAM has been a real showstopper for me. Until now the only way to setup centralized authentication and roaming profiles is to use a combination of NIS and NFS, which is far from ideal in terms of security. I suggested the inclusion of PAM in a public poll in the Slackware forum on LinuxQuestions.org, which got mixed results. About half of the Slackware users welcomed the idea, the other half got pretty angry, and the result turned into a flamefest. The idea had been to somewhat open up Slackware to the enterprise world, but as far as I can reckon, the word "enterprise" curiously enough seems to have a bad taste for a significant portion of Slackware's user base. After this heated exchange, I decided to take a pragmatic approach and choose a more appropriate tool as a base for my business. So here I am. Cheers, Niki PS: after a few years on LQ, the general tone on the CentOS mailing list seems like the Alban Berg Quartet after Slayer at Hellfest. :o) -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32
On Wed, Mar 11, 2015 at 7:37 AM, Niki Kovacs <info at microlinux.fr> wrote:>> > After this heated exchange, I decided to take a pragmatic approach and > choose a more appropriate tool as a base for my business. So here I am.Yeah, businesses have this weird idea that if something works right, it should just keep working for the life of the business... By the way - if you are new to Centos and RH-style in general, you might want to look at how much of the local configuration settings are abstracted into files under /etc/sysconfig/. I'm not sure if slackware used that at all since it is a SysVinit concept - or how it will evolve with the change do systemd, but generally for the packages that pick up option settings there you can avoid editing the main config files and setting up conflicts with future rpm updates. It's not perfect but it helps. -- Les Mikesell lesmikesell at gmail.com