List Info

Thread: BLFS install tracking
BLFS install tracking
user name
 2006-06-14 17:52:02 
Manuel,
   The TODO list has an entry for tracking previously
installed 
packages. Currently I touch a file /var/lib/jhalfs/BLFS/xxx
for each 
package installed and when a new package makefile is created
if a 
dependency is already installed it is not included in the
new makefile. 
The resulting makefile touches a file for each new package
installed.
   (We don't want to re-invent the wheel and create a full
package 
manager for BLFS do we?)

  Pros:
   ???

  Cons:
.  The tracking is only done when the makefile is created.
If you rerun 
an old makefile it will run normally because it has no
knowledge of 
previously installed packages.
.  The BLFS scripting system does not play well with other
methods. ie: 
if you manually install a package there is no automatic
install 
tracking. (as with any package manager system)


Note: It is possible to install tracking inside the
makefile, to check 
for previous package installs.

G
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
BLFS install tracking
user name
 2006-06-14 19:22:57 
El Miércoles, 14 de Junio de 2006 19:52, George Boudreau
escribió:
> Manuel,
>    The TODO list has an entry for tracking previously
installed
> packages. Currently I touch a file
/var/lib/jhalfs/BLFS/xxx for each
> package installed

That looks fine for now.

> and when a new package makefile is created if a 
> dependency is already installed it is not included in
the new makefile.

Some way to can output on the screen the list of skipped
packages could be 
needed.

The user may want to reinstall some of them to satisfy
circular dependencies 
or to upgrade to a new version, Then he need to know if the 
relevant /var/lib/jhalfs/BLFS/xxx need be deleted and the
Makefile 
regenerated.

> The resulting makefile touches a file for each new
package installed.
>    (We don't want to re-invent the wheel and create a
full package
> manager for BLFS do we?)

Not, but we need to allow the users to can create a full
GNOME desktop system 
in small chunks instead to force it to review/edit in one
session all that 
amount of build scripts required to run a gnome-full
Makefile.

Some way to can compare installed versions with current book
versions will be 
nice, but not required for the current POC code, IMHO.

>   Cons:
> .  The tracking is only done when the makefile is
created. If you rerun
> an old makefile it will run normally because it has no
knowledge of
> previously installed packages.

No problem. In that hypothetical scenario, the user could
regenerate that old 
Makefile to keep it updated. (If the user have an old
Makefile, he must have 
also the associated build scripts).

> .  The BLFS scripting system does not play well with
other methods. ie:
> if you manually install a package there is no automatic
install
> tracking. (as with any package manager system)

The user can allways to create manually the required
/var/lib/jhalfs/BLFS/xxx 
files to keep that "database" up-to-date.

That looks like an improvemment over package managers 


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.com
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
BLFS install tracking
user name
 2006-06-14 20:44:25 

M.Canales.es wrote:
> El Miércoles, 14 de Junio de 2006 19:52, George
Boudreau escribió:
> 
> The user may want to reinstall some of them to satisfy
circular dependencies 
> or to upgrade to a new version, Then he need to know if
the 
> relevant /var/lib/jhalfs/BLFS/xxx need be deleted and
the Makefile 
> regenerated.
> 
>> The resulting makefile touches a file for each new
package installed.
>>    (We don't want to re-invent the wheel and
create a full package
>> manager for BLFS do we?)
> 
> Not, but we need to allow the users to can create a
full GNOME desktop system 
> in small chunks instead to force it to review/edit in
one session all that 
> amount of build scripts required to run a gnome-full
Makefile.
> 
> Some way to can compare installed versions with current
book versions will be 
> nice, but not required for the current POC code, IMHO.

   Could you extract the package version number and place it
in the 
build script as a variable ie: PKG_VERSION=1.2.3 . I could
extract the 
value and use it when the makefile is created for version
comparison. 
When the makefile is run it could
   touch /var/lib/jhalfs/BLFS/pkgname-$PKG_VERSION

   It is not necessary to utilize the version number today
but it would 
be nice for the future..

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
BLFS install tracking
user name
 2006-06-14 20:56:31 
El Miércoles, 14 de Junio de 2006 22:44, George Boudreau
escribió:

>    Could you extract the package version number and
place it in the
> build script as a variable ie: PKG_VERSION=1.2.3 . 

I will try it after finish the download code. 

> I could extract the 
> value and use it when the makefile is created for
version comparison.
> When the makefile is run it could
>    touch /var/lib/jhalfs/BLFS/pkgname-$PKG_VERSION

Or maybe

echo $PKG_VERSION > /var/lib/jhalfs/BLFS/pkgname

-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.com
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
BLFS install tracking
user name
 2006-06-14 21:09:28 

M.Canales.es wrote:
> El Miércoles, 14 de Junio de 2006 22:44, George
Boudreau escribió:
> 
>>    Could you extract the package version number and
place it in the
>> build script as a variable ie: PKG_VERSION=1.2.3 . 
> 
> I will try it after finish the download code. 
> 
>> I could extract the 
>> value and use it when the makefile is created for
version comparison.
>> When the makefile is run it could
>>    touch /var/lib/jhalfs/BLFS/pkgname-$PKG_VERSION
> 
> Or maybe
> 
> echo $PKG_VERSION > /var/lib/jhalfs/BLFS/pkgname
   yup.. works for me
> 
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
BLFS install tracking
user name
 2006-06-14 20:59:33 
El Miércoles, 14 de Junio de 2006 22:56, M.Canales.es
escribió:

> Or maybe
>
> echo $PKG_VERSION > /var/lib/jhalfs/BLFS/pkgname

Actually, we know the full package name, thus maybe

 echo $PACKAGE > /var/lib/jhalfs/BLFS/pkgname

could work for now.

-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.com
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
[1-6]

about | contact  Other archives ( Real Estate discussion Medical topics )