Hi Jerry,
I would be interesting to specify a prefix directory to create the
instal directory path.
It could be used like that:
$> packager -P /opt
then in package.qpg
I don’t know if we really need a variable in the QPG file or if the
prefix can be assumed automatically.
For the x86 processor prefix, for example, I think that you said it is
optional, packager should guess it from the elf file.
Maybe the install prefix should be accessible in the pkg-installer, I
think rpm allow that. In that case, $PREFIX could be set in QPG file as
a default install dir () and then being
changed through the pkg_installer.
These requirements because we will have more and more portage of Unix
application and you know that installation directory is something a bit
shambolic in Unix.
So for the case where we would add a package.qpg in future distribution
release, we’d need a more flexible packager.
In the same idea, we need an option to set the version number instead of
.
Maybe something like ‘packager -Q ReleaseVersion 1.9.1 -Q
anyOtherQPGTag’ would be cool.
cheers,
Alain.
Thanks for the suggestions, I’ll make note of them for possible features for
a future release.
Jerry
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3F55D423.4080102@icbt.com…
Hi Jerry,
I would be interesting to specify a prefix directory to create the
instal directory path.
It could be used like that:
$> packager -P /opt
then in package.qpg
QPG addfile file="…" install="$PREFIX/whateverwewant/"/
QPG addfile file="…" install="/x86/$PREFIX/whateverwewant/"/
I don’t know if we really need a variable in the QPG file or if the
prefix can be assumed automatically.
For the x86 processor prefix, for example, I think that you said it is
optional, packager should guess it from the elf file.
Maybe the install prefix should be accessible in the pkg-installer, I
think rpm allow that. In that case, $PREFIX could be set in QPG file as
a default install dir () and then being
changed through the pkg_installer.
These requirements because we will have more and more portage of Unix
application and you know that installation directory is something a bit
shambolic in Unix.
So for the case where we would add a package.qpg in future distribution
release, we’d need a more flexible packager.
In the same idea, we need an option to set the version number instead of
QPG ReleaseVersion/>.
Maybe something like ‘packager -Q ReleaseVersion 1.9.1 -Q
anyOtherQPGTag’ would be cool.
cheers,
Alain.