[Slackbuilds-users] krb5 slackbuild
rworkman at slackbuilds.org
Thu Jul 2 17:03:55 UTC 2009
On Fri, 26 Jun 2009 12:51:03 -0400
Tom Canich <tcanich at canich.net> wrote:
> On Wed, Jun 24, 2009 at 05:19:57PM -0500, Robby Workman wrote:
> > On Tue, 2 Jun 2009 22:41:44 -0300
> > Oda <edu.oda at gmail.com> wrote:
> > > I was writing a slackbuild to krb5 when somebody submit one, so I
> > > decided to wait. But this slackbuild is still in the pending list.
> > >
> > > Is there any problem with it? Maybe I can help.
> > Well, the original submission had some conflicts with other
> > Slackware packages, and there are now two proposals to resolve
> > those conflicts. I hammered out one earlier today, and the original
> > submitter (Tom Canich, CC'd on this mail) has another. I don't
> > know which is better, to be honest- so long as both work, either is
> > fine with me. The one I hammered out is here:
> > http://slackbuilds.org/krb5.tar.gz
> > Please have a look and see what you guys think; feedback is
> > welcome, and I'd like to get this into the repo for 12.2 if at all
> > possible. Tom's waited long enough as is.
> Sorry for the delayed reply. I have been away from email for a few
> Thanks for your work on this, Robby. I don't mind waiting -- my only
> concern is producing a quality package! :)
> Am I correct that your solution is to drop the "et" stuff, rename
> rsh, ftp, and telnet to include a .krb5 suffix? I agree there is
> probably no reason to include the "et" stuff -- I don't think it does
> anything differently from the software already shipping with
> My only concern with this solution is portability. Scripts written
> for other platforms should not require significant modification to
> work on Slackware. Renaming some programs (or all programs) may
> require significant changes.
> The solution I proposed is an alternate prefix, /usr/kerberos. This
> is the prefix used on RedHat EL systems*. This way only the PATH
> need be specified for a script to work on any platform. The program
> names will remain the same.
Okay, I decided to go with your solution, as the approach does make
more sense. I'm about to push this out along with a few other things
for our 12.2 repo; if it's not exactly right, we'll fix it up.
Ideally, this will be our final push to slackbuilds/12.2/ :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: not available
More information about the SlackBuilds-users