netzary / neatx

Automatically exported from code.google.com/p/neatx
0 stars 0 forks source link

neatx.spec file has version 0.1, not 0.3.1, and other issues #64

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. ./autogen.sh
2. ./configure
3. make dist-gzip
4. rpmbuilt -ta neatx-0.3.1.tar.gz

What is the expected output? What do you see instead?
    neatx.spec looks for tarball neatx-0.1.tar.gz, and expects software to be in tarball without leading 'neatx-%{version}.

What version of the product are you using? On what operating system?
    Revision 59 of the Subversion trunk.

Please provide any additional information below.
    Fixing this, along with including all the necessary files in Makefile.am from a separate bug report, will allow 'rpmbuild -ta' on the tarball to completely build this tool in RPM based systems.

    I'm attaching a .spec file that also addresses all of these issues. I'll submit them separately if needed.

* Updated the 'Version' to 0.3.1. Ideally, this would be generated by autoconf, 
but rewriting the Makefiles to generate this right now is beyond the time I 
have for this.

* I've reduced the 'pygobject2' requirement to 2.12, to allow RHEL 5 
compilation.

* I've reset the "Requires:" for "ssh-clients" and "ssh-server", not "openssh", 
which allows the use of OpenSSH clients such as Centrify's packages.

* I've added 'Conflicts: freenx-server', which also uses the 'nx' user but with 
very different settings and should not be installed in parallel to neatx.

* I've changed the '%setup' line to be more verbose, and to handle that tarball 
name change.

* Having the "nx homedir" under /var/lib/neatx causes ownership and packaging 
issues. I've moved that aside to /var/lib/nx.

* I've reset the __install to use 4 digit permission settings, which just keeps 
things more consistent for .spec files I work with.

* When doing the '%pre' steps, I do not create a homedir for nx: those homedir 
comes from the RPM. This is not a normal user account and doesn't need .bashrc 
nad /etc/profile.d/ settings, nor should it have them. Instead, the directories 
and authozed_keys configuration file are directly in the %files stanza.

* When doing the '%pre' steps, check for an nx user with an unexpected homedir, 
which will cause chaos if relocated.

* I've removed the %post steps that redeployed and overwrite existing 
authorized_keys files. That's a local configuration environment, and now marked 
as a '%config(noreplace)" file.

* I've moved the neatx init script deployment to /etc/rc.d/init.d/neatx, which 
is where the file really goes. /etc/init.d is a symlink, and direct RPM 
manipulations written to there have caused endless grief when someone 
accidentally breaks the link and starts putting init scripts in the wrong place.

* I've refined the permissions of the 'nx' user's home directory and .ssh 
directory to be 0700.

Original issue reported on code.google.com by nka...@gmail.com on 30 Sep 2010 at 3:18

Attachments: