Coordinate manual installs

[bdubbs@…]

I am not sure if this is covered or not. I have not studied the jhalfs internals so if it is, mark invalid.

I would like to use jhalfs-blfs to incorporate packages I have already built manually. It might be as simple as referring to a file where manually built packages are listed. For instance:

$ cat files-built
lsb-release-1.4
libffi-3.2.1
Python-3.6.2

etc

It might also be useful to have a timestamp associated with each file. I do that now with my build scripts.

[Pierre Labastie]

Thanks for your suggestion. I am not sure what you mean "using jhalfs-blfs" ;-) I understand you had built packages manually, then you added jhalfs-blfs, and now, you want those manually built packages to be known to jhalfs. Or maybe, you had built lfs with jhalfs-blfs, but then built some package manually. If this is what you mean, it is covered in README.BLFS, 3.1 INSTALLATION ON A RUNNING SYSTEM: using the example you give, type:

cd /var/lib/jhalfs/BLFS
touch lsb-release-1.4
touch libffi-3.2.1
touch Python-3.6.2
cd ~/blfs_root
make

(adjust directories if you have changed the defaults). The manually installed packages should now appear in /var/lib/jhalfs/BLFS/inspkg.xml.

Now for the timestamp, I guess there is nothing right now in jhalfs-blfs. Could you explain what you'd like to see?

[bdubbs@…]

So I think what you are saying is that what is needed is:

TRACKING=/var/lib/jhalfs/BLFS
touch $TRACKING/<package>-<installed-version>
# Repeat as appropriate

and at that point jhalfs will understand that the package is already installed. Am I reading that correctly?

Also, would there be a problem if there are more than one entry like:

pkg-name-1.2
pkg-name-1.3

[Pierre Labastie]

Replying to bdubbs@…:

So I think what you are saying is that what is needed is:

TRACKING=/var/lib/jhalfs/BLFS
touch $TRACKING/<package>-<installed-version>
# Repeat as appropriate

and at that point jhalfs will understand that the package is already installed. Am I reading that correctly?

Yes

Also, would there be a problem if there are more than one entry like:

pkg-name-1.2
pkg-name-1.3

I've never tried, but I guess the last entry (in lexicographic order) will be taken.

[bdubbs@…]

OK, let's close this as invalid. It's covered in the documentation.