Re: [Paco-general] Format of the log file ?

[Kevin W. <kev...@gm...>]

Hi David,

Sorry for the late reply and thanks again for your time and help.

> Mmm... this is an obscure and known bug. It occurs when you try to log a
> package from within the sources directory of a different package. In your
> case, you probably logged sip from the sources directory of pcre, and paco
> read the pcre's config.log thinking it was the sip's one.
>

Yes, I seemed to have missed that one ! :-) 

I didn't realize that I were in pcre sources directory ! Apologize for my 
ignorance ! :-)  Yes, you were right. I just tried logging from from my home 
directory and paco didn't include the config line at all. So, that's OK. 
Thanks for pointing out.

> Sizes are apparent by default. This is because I appreciate that the size
> given by "paco -ast" is as close as possible to that of  "df -h". If you
> want sizes to be the "real" ones, just set  BLOCK_SIZE=1 in pacorc, and
> update the database with "paco -au".

Unfortunately, that didn't work for me. I set BLOCK_SIZE=1 in pacorc and 
updated database "paco -au". That did update the log files but, the sizes I 
see in the log files are still apparent sizes and not the real ones. It 
doesn't seem to be working for some reason. Even with the installtion of new 
packages, only apparent sizes are being logged ! Any ideas ?

> As you know this is not possible by now, and I don't plan to add that
> feature in the future.
> If you don't want the documentation or the locale data to be logged, just
> use the option --exclude when logging a package, passing it the appropiate
> arguments, or use the variable EXCLUDE in pacorc if you want a more
> permanent setting.
>
> For instance:
>
> $ paco -lp foo --exclude="/usr/share/doc:/usr/share/locale" make install
>

Well, it doesn't hurt me in anyway as, I can manually edit/update the log 
files.

Thanks for the help with "--exclude" switch. I didn't know it could work with 
files too. I presumed it worked only with directories ! That is convenient 
way of excluding files which are not meant to be logged ! :-)

Thanks for your help again and best regards,

Kevin

On August 16, 2007 13:27:41 David Rosal wrote:
> Hello Kevin.
>
> 2007/8/13, Kevin Williams <kev...@gm...>:
> > Hi David,
> >
> > Thanks a million for you detailed response. I really appreciate it.
> >
> > > > This works except the fact that, the configure options used for the
> > > > compilation are actually copied from that of the paco itself.
> > >
> > > I don't understand this.
> >
> > What I meant was that, when I create a paco log file from a file
> > containing
> > the list of files for a package already installed using the command
> > below, paco seems to copy the config line of the last package installed.
> >
> > cat <pkg-list-file> | paco -lp <pkg-name>
> >
> > For eg. when I installed sip-4.7 I created a file contanting the list of
> > files
> > installed by sip's 'make install'. Later, I ran paco as above to generate
> > a
> > paco log file for sip-4.7. The sip-4.7 log file contains the following
> > configure line:
> >
> > #c:--docdir=/usr/share/doc/pcre-7.2 --enable-utf8 --prefix=/usr
> > CFLAGS=-mtune=pentium4m -march=pentium4m -msse2 -pipe -fomit-fr
> >
> > As you can see, it apparently copied that line from the pcre-7.2 log file
> > which was the most recent log file in /var/log/paco.
>
> Mmm... this is an obscure and known bug. It occurs when you try to log a
> package from within the sources directory of a different package. In your
> case, you probably logged sip from the sources directory of pcre, and paco
> read the pcre's config.log thinking it was the sip's one.
>
> Well, it is really not an issue, as I found out what the 2nd and 3rd lines
>
> > of
> > the log file mean. Before this, I didn't know what the 2nd and 3rd lines
> > in
> > the log file were, I thought of them to be some sort of checksum for the
> > logfile itself. So, I was a bit reluctant to modify the log file by hand.
> >
> > I'm just laying out my understanding of 2nd and 3rd lines of the logfile,
> > please correct me if I'm wrong.
> >
> > The 2nd line consists of 4 fields delimited by '|'
> >
> > The first is the total size of package
> > The second field is 'size missing'
> > The third field is 'No. of files the package contains'
> > The fourt field is 'Files Missing'
> >
> > The 3rd line stores the time stamp in 'seconds in epoch' format.
>
> You're right.
>
> All these things became clear when, I launched gpaco !! :-)
>
> > I couldn't help wonder as to why are the sizes are apparent sizes and
> > hence,
> > not the actual file sizes ?!
>
> Sizes are apparent by default. This is because I appreciate that the size
> given by "paco -ast" is as close as possible to that of  "df -h". If you
> want sizes to be the "real" ones, just set  BLOCK_SIZE=1 in pacorc, and
> update the database with "paco -au".
>
> > Also, I thought there should be a way to just remove aline from the
> > logfile.
> > There're cases when, I don't want documentation installed in other
> > languages
> > besides english and hence, I normally delete those files. I can do so
> > with paco or gpaco but, paco log files still contain the references to
> > the removed
> > files and thus add to the overhead. There should be a way to just delete
> > these files and not have any references/records of them at all. Ofcourse,
> > this is just my opinion.
>
> As you know this is not possible by now, and I don't plan to add that
> feature in the future.
> If you don't want the documentation or the locale data to be logged, just
> use the option --exclude when logging a package, passing it the appropiate
> arguments, or use the variable EXCLUDE in pacorc if you want a more
> permanent setting.
>
> For instance:
>
> $ paco -lp foo --exclude="/usr/share/doc:/usr/share/locale" make install
>
>
> Cheers.
>
>
>     *david