Problem of install tarball packages

[Richard England]

Craig White wrote:
> On Fri, 2008-09-26 at 20:35 -0700, Kam Leo wrote:
>   
>> On Fri, Sep 26, 2008 at 7:49 PM, Craig White <craigwhite at azapple.com> wrote:
>>     
>>> On Sat, 2008-09-27 at 10:26 +0800, edwardspl at ita.org.mo wrote:
>>>       
>>>> Craig White wrote:
>>>>         
>>>>> On Sat, 2008-09-27 at 01:43 +0800, edwardspl at ita.org.mo wrote:
>>>>>
>>>>>           
>>>>>> Aldo Foot wrote:
>>>>>>
>>>>>>             
>>>>>>> On Fri, Sep 26, 2008 at 10:13 AM, Craig White <craigwhite at azapple.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>>> On Sat, 2008-09-27 at 01:10 +0800, edwardspl at ita.org.mo wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> Aldo Foot wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>>>> On Fri, Sep 26, 2008 at 9:34 AM,  <edwardspl at ita.org.mo> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>>>> Dear All,
>>>>>>>>>>>
>>>>>>>>>>> How to config the sudo, then allow user A to install tarball packages with FC8 System ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>> You use the 'visudo' command to edit the /etc/sudoers files.
>>>>>>>>>> Don't edit that file directly.
>>>>>>>>>>
>>>>>>>>>> see this /etc/sudoers sample
>>>>>>>>>> http://www.gratisoft.us/sudo/sample.sudoers
>>>>>>>>>>
>>>>>>>>>> 'rpm' is just another command you add to the allowed commands.
>>>>>>>>>> so for example a the CLI: "sudo rpm -Uvh someRpm.rpm',
>>>>>>>>>>
>>>>>>>>>> ~af
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>> Hello Aldo,
>>>>>>>>>
>>>>>>>>> Sorry, my means is tarball packages ( NOT rpm packages )...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>> ----
>>>>>>>> users don't need superuser privileges to use tar at all UNLESS they are
>>>>>>>> trying to 'untar' into spaces where only superuser can write, in which
>>>>>>>> case, security is out the window.
>>>>>>>>
>>>>>>>> Craig
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> You're correct. How did I mix rpm and tar? My coffee was not strong
>>>>>>> enough this morning.. ;-)
>>>>>>>
>>>>>>> ~af
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> Hello,
>>>>>>
>>>>>> Sorry, My means is how to running the command line of "./configure",
>>>>>> "make" and "make install" ?
>>>>>> How to config sudo or / and linux system for it ?
>>>>>>
>>>>>>             
>>>>> ----
>>>>> users can (and should) run configure, make as users, not as super users.
>>>>> 'make install' only needs super user privileges if the intended install
>>>>> is to go into /usr/local but users can have 'bin' or 'sbin' directories
>>>>> in their own space to run compiled programs that are available only to
>>>>> that specific user and not to all users.
>>>>>
>>>>> Did I mention that you are going to have nightmares if you actually give
>>>>> users super user privileges enough times yet?
>>>>>
>>>>> Craig
>>>>>           
>>>> Hello,
>>>>
>>>> When I tried to install the tarball packages as the following :
>>>>
>>>> [svradmin at svr1 proftpd-1.3.0a]$ ./configure --prefix=/usr/local/proftpd
>>>>
>>>> ./configure: line 88: conf4161.sh: Permission denied
>>>> ./configure: line 89: conf4161.sh: Permission denied
>>>> chmod: cannot access `conf4161.sh': No such file or directory
>>>> ./configure: line 201: conf4161.file: Permission denied
>>>> ./configure: line 1266: config.log: Permission denied
>>>> [svradmin at svr1 proftpd-1.3.0a]$
>>>>
>>>> So, how to fix the problem ( Permission denied ) ?
>>>>
>>>> Any solution for it ?
>>>>         
>>> ----
>>> sure, make sure the same user/group that 'untarred' the tarball and owns
>>> the files/folders is the one trying to run 'configure'
>>>
>>> Craig
>>>       
>> The directory "/usr/local/" is owned by root. The OP needs to have
>> root's permissions. He can use either sudo or su get get root's
>> permissions or use a target directory to which he has read and write
>> access.
>>     
> ----
> does that matter though if all you are running is ./configure ?  I never
> had a problem with that.
>
> Craig
>
>   
I believe this depends on what .configure does to determine what is 
needed to set up the configuration.  If the tests require creation of 
files etc. then you might encounter issues like this.

~~R