Jeff- Jeff Wrote: > > My suggestions for useradd: Make sure that the home directory does NOT > exist (if it does, you likely don't want to use the option to create > the home directory - in fact, you likely want to just skip creation of > the account in that case, as it would likely exist). > That's why I thought not having a home directory was a good idea. The way this RPM works, /usr/local/slimserver is created by RPM itself when installing the files and possibly a second time by useradd, causing the error. Without the directory created, useradd worked from the command line. I've inspected the source code for useradd to look into it, but need to experiment some.
> I see your information on how to create an RPM - is this for an RPM or > for an SRPM? And what was the reasoning for doing an SRPM vs. an RPM? > (I'm far from an RPM wizard; I've used both, and strictly speaking, I > suppose slimserver is more of an SRPM than an RPM - although I'm not > certain this is true with the CPAN stuff. Please bear with me during my answer to this...I may have over-simplified this. I've packaged up dozens of RPMs for fedora containing software that is not part of extras or other repositories *compatible* with extras. My usual model for creating RPMs is to start with the source code for my project and write a .spec file or modify one for another distribution. Rarely do I get the spec file right off the bat... always some fiddling required. For complex software packages, it has taken as many as thirty edits of the spec file to get it right. The problem with installing the slimserver RPM on FC5 is in the spec file, and the spec file is deleted after the stock makerelease.pl script creates the RPM. Also, binary RPM's don't have the spec file, which is why rpm2cpio didn't help you. SRPMs do. Also, makerelease.pl is not exactly a speed demon (doesn't need to be). That's why I modified it to create an SRPM; it simplifies and speeds debugging the spec file. You can install the SRPM with rpm -i <SRPM> and it will be in your rpm build tree... sounds like you're familiar with that, but if you're not, you can use the fedora-buildrpmtree package (see http://fedoraproject.org/wiki/fedora-rpmdevtools) to make one. Then you can make incremental changes in the spec file until it's working. At this point, you usually just package the rpm and you're done. But for slimserver, the .spec.build file will need to be changed so that makerelease.pl outputs the spec file as you want it. > If the CPAN stuff has compiled code for C <-> PERL interfaces, then > it's really a RPM, not an SRPM.) That's correct... the RPM doesn't depend on the system on which slimserver is being installed having a c compiler, so the SRPM isn't *really* an SRPM, but the point is being able to incrementally modify the spec file and test it with fewer steps, making this a matter of semantics. Also, if you want to do away with the CPAN stuff within slimserver and use the system libraries, a SRPM is where you would start paring away. Which brings up the question, would slim devices support a yum repository with a fedora-specific package to simplify all this stuff for FC5? I haven't had time to work on this since Saturday and looks like I won't for a while (headed out of town), but it will be a priority when I'm back. -al -- Al Pacifico ------------------------------------------------------------------------ Al Pacifico's Profile: http://forums.slimdevices.com/member.php?userid=5640 View this thread: http://forums.slimdevices.com/showthread.php?t=23594 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
