> Bingo. And it would be unwise, from a security perspective, to allow > perl to look there for libraries.
I don't get your point actually, Matt :) I've build plenty of packages in such way and it never fails unless install script has a bug.
Correct. However, in this case, the install script actually invokes razor, see below.
Come on man :) just forget about that '/tmp'! Let's say I'd like to install it to DESTDIR=/opt/razor. It fails with the same error. Shell I also check it with DESTDIR=/usr/razor for you? :>
No, although adding /opt/razor to your perl @INC wouldn't constitute a security hole, it won't help.
Bear in mind my complaints about /tmp *only* pertain to an execution environment. Since you are repackaging (despite your claims otherwise, it is what you are doing, building a slackware package from a tarball) that's perfectly legit. Read on.
> You're trying to EXECUTE razor from that location, not just build a > package out of it.
Why do you say I'm trying to execute razor? I just make install, that's it. Please read my first message carefully.
Fair enough. I've re-read and you're not trying to execute it.. The make install process actually executes the razor_client.. ick.
This is a bit of a bug in the install script, or at least horribly ugly abuse of perl code built into Razor::Client::Agent to do something the makefile should do itself. They're making symlinks by executing the full-blown razor-client. It detects the absence of symlinks and creates them.
I'd assumed when I saw signs of razor-client being invoked you'd done so yourself. I was wrong on that.
Let's see if I can help some:
It looks like "make install" does all of the following: "make all" "make pure_install" "make doc_install" and "make install_razor_agents"
The last line in your output before the error is "Appending installation info to", which is the end of make doc_install.
make install_razor_agents appears to execute the new razor_client file, but it seems it only does so to create symlinks to the script... (razor-check, razor-report, razor-revoke, and razor-admin). Clearly executing razor_client before the razor perl libs wind up where they need to be isn't going to work.
In theory, you could run all the sub-steps, with your DESTDIR in /tmp, and exclude the "make install_razor_agents".
From there, you can wrap a slackware package and install that. After that, execute /usr/bin/razor-client and it should create the symlinks.
The slackware package won't be aware of the symlinks, but that's not too tragic.
The alternative is to ln -s the symlinks yourself (all of the above 4 names are symlinks to /usr/bin/razor-client) and then wrap the package and install it.
> If you're just repackaging, that's one thing.. go for it.
No, I'm not repackaging. I'm building razor from scratch. Matt, please read my first message to the mailing list carefully.
Actually, you are repackaging... You're repackaging the razor source tarball as a "binary" slackware package. However, you are only doing so as a waypoint of your install process.
ie: you intend to build and install razor into /tmp, repackage it as a slackware package using slackpack, then install that. Right?
That's what I mean by repackaging.. Converting one form of package (in this case the source tarball) into a installable package for your OS package manager.
If you weren't repackaging, you'd just do make install without a destdir, but this would make your slackware package system unaware of razor. Hence the intermediate repackaging step to make slackware aware of it.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
