On Tue, 10 Apr 2012 00:08:30 +0100
Fernando de Oliveira <fam...@yahoo.com.br> wrote:

> On 09-04-2012 16:14, andy@... wrote:
> > Author: andy
> > Date: 2012-04-09 13:14:47 -0600 (Mon, 09 Apr 2012)
> > New Revision: 9888
> >
> > Modified:
> >    trunk/BOOK/xsoft/office/libreoffice.xml
> > Log:
> > Libre Office tweaks.
> > The dependencies are still a work in progress.
> >
> ...
> > +    <warning>
> > +      <para>
> > +        Untaring the libreoffice-core-3.5.2.2 tarball as
> > +        <systemitem class="username">root</systemitem> has the curious 
> > effect of
> > +        changing the ownership of the <emphasis>parent</emphasis> directory
> > +        to a user with numerical id 11012 and with the permissions set to 
> > allow
> > +        read, write and execute for that user only! If you untared as
> > +        <systemitem class="username">root</systemitem> in your home folder 
> > you
> > +        could end up unable to log in again. If you untared it in
> > +        <filename class="directory">/usr</filename> you would find your 
> > user
> > +        account unable to access any file in
> > +        <filename class="directory">/usr</filename> :/
> > +      </para>
> > +
> > +      <para>
> > +        You can avoid this unpleasantness by
> > +        <emphasis>not</emphasis> untaring it as
> > +        <systemitem class="username">root</systemitem>. If you must untar 
> > it as
> > +        <systemitem class="username">root</systemitem> pass the option
> > +        <option>--no-overwrite-dir</option> to tar. This is the default 
> > when you
> > +        untar as a user but has to be passed as an option when untaring as
> > +        <systemitem class="username">root</systemitem>:
> > +      </para>
> > +    </warning>
> > +
> > +<screen role="root"><userinput>tar xf --no-overwrite-dir 
> > libreoffice-core-&libreoffice-version;.tar.xz &amp;&amp;
> > +cd libreoffice-core-&libreoffice-version;</userinput></screen>
> > +
> >      <para>
> >        Install <application>Libre Office</application> by running the 
> > following
> >        commands:
> >
> Sorry, I did not know about that, always use $TMPDIR/$BUILDDIR, usually 
> TMPDIR=/home/fernando/tmp and tmp is a link to a directory in another HD 
> (after LO once filled up my main HD), and BUILDDIR=paco-build-`date 
> +%Y.%m.%d`; for kernel upgrade, no BUILDDIR, but 
> TMPDIR=/home/fernando/tmplinux, so the sources are later moved to /usr/src, 
> and it took too long, when was in the auxiliary HD.

No worries. At least I caught it before the book rendered. I did most
of my testing as a user so I didn't catch the problem with the tarball
until near the end when I came to install it as root and strange things
started to happen...
Hopefully the problem will be fixed in the next version/tarball and the
ugly warning can be removed from the page.

> About dependencies:
> 
> I have a doubt if LO uses curl or wget...

It seems that the download script requires either curl or wget and
configure has the option --with-system-curl

Andy
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to