Date: Wed, 04 Jul 2001 11:31:00 +0200 From: Cynic <cynic@mail.cz> To: "David W. Chapman Jr." <dwcjr@inethouston.net>, <freebsd-ports@freebsd.org> Subject: Re: samba port install failure... general question Message-ID: <5.1.0.14.2.20010704111952.01f655f8@mail.cz> In-Reply-To: <014b01c10283$f944ede0$fe0c4042@inethouston.net> References: <5.1.0.14.2.20010701231030.020399d0@mail.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there,
At 01:17 7/2/2001, David W. Chapman Jr. wrote the following:
--------------------------------------------------------------
>> is there a reason for a port to assume it's installed in
>> /usr/local? I just tried to build samba-devel, and it failed,
>> because there's no /usr/local/samba/share/ (the command line
>> was # make PREFIX="/usr/local/samba" install, Makefile contains
>>
>> post-install:
>> ${MKDIR} ${PREFIX}/share/examples/samba
>>
>PREFIX is not always /usr/local, but you can assume that the ports system
>wants to install into a PREFIX that looks like /usr/local or it will try to
>make your PREFIX look like /usr/local basically.
# make PREFIX=/tmp/samba install
succeeded indeed, so it's the constraints stuff you mention below
>> and other things like that, and # make install failed with
>>
>> Installing SWAT in /usr/local/samba/share/swat
>> Installing the Samba Web Administration Tool
>> mkdir: /usr/local/samba/share: No such file or directory
>> Failed to make directory /usr/local/samba/share/swat, does root
>> have privileges?
>>
>This would be because ports can't modify directories under /usr/local or
>create them for that matter(to the best of my knowledge, I"m sure someone
>more knowledgeable could comment). If you want it installed in
I don't understand why this is so. The ports stuff requires one to be
logged in as root anyway, so why should it be designed so that one cannot
install a port where they want?
>/usr/local/samba, just download the tarball and compile it to avoid this
>problem if you absolutely need it in /usr/local/samba, but that's not the
>best place for it, where the port puts it is probably the place you would
>want it 95% of the time.
Well, that depends, I guess. Clobbering /usr/local with loads of software
is not what I'd like to achieve.
>> I tried to workaround the limitation with this:
>>
>> [toor(root)@freepuppy samba-devel]# mkdir /usr/local/samba/share
>> [toor(root)@freepuppy samba-devel]# make clean
>> [toor(root)@freepuppy samba-devel]# make PREFIX="/usr/local/samba" build
>> [toor(root)@freepuppy samba-devel]# make install
>>
>If you run
>
>mkdir /tmp/samba
>make clean install PREFIX=/tmp/samba
>
>that will prove that they don't assume PREFIX=/usr/local
>
> From my understanding ports can't modify anything under /usr/local that
>doesn't already exist and that's where your problem lies. So a solution for
>you would be to let it install it where it wants or compile it from the
>source.
Is this documented anywhere? And what is the rationale? I surely couldn't
find anything related in the Handbook or Porter's Handbook.
Thanks for your reply
cynic@mail.cz
-------------
And the eyes of them both were opened and they saw that their files
were world readable and writable, so they chmoded 600 their files.
- Book of Installation chapt 3 sec 7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20010704111952.01f655f8>