Re: Building same package twice and package forking

--===============2114542523==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X"
Content-Disposition: inline


--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 12.11.2006 07:29:29, Luca wrote:
> Hi all!

Hello.

> I'm creating LinuxFromScratch (http://www.linuxfromscratch.org) and its
> projects (BeyondLinuxFromScratch, HardenedLinuxFromScratch,
> Cross-LinuxFromScratch and BeyondCross-LinuxFromScratch) targets but I'm
> having some problems in installing some packages.
> Under the documentation I found the
> How_To_Install_the_same_package_twice and the Package_Forking but I
> haven't managed to make it works.
> For the install the same package twice the examples are given using mine
> and Build-Package.

`mine' is used in that example to get the current installed version of a
package:

# mine -q package
package version

And to later uninstall a package:
# mine -r -s -v package

These are not necessary to install a package twice. What's important is the
forked package name (the part after the equal sign).

> In LFS we use to build same packages twice (example in stage0 and stage1
> we use a Binutils-Pass 1, Gcc-Pass1, then some other packages, an
> Adjusting the Toolchain phase and after some packages we have a
> Gcc-Pass2 and Binutils-Pass2 and then the rest of packages).
>=20
> My question is: can the package forking be used in conjunction with
> Build-Target script to let  the automated-system-build take care of the
> these double-passes (I meant, but I think it's understood, I need to
> have these packages to build twice under the same stage but with two
> different priorities);
> Now then the question about package forking: I read in the
> Package_Forking about the Conditional  .desc files and took a look at
> the Desc_file_syntax. The examples show the conditions for the use with
> $xpkg; so I would like to know if it's possible to use conditions with
> the $target (example: one target has a x.x.0 version of a package, while
> another target has the x.x.1 version of the same package) ?

I don't really understand why you want to build the same package twice in
one stage. Currently the compile toolchain packages are built 3-4 times
in various stages: 0, 1, 5 for most. Could you elaborate a bit on this?
As of now, it's not possible to build a package twice under different fork
names with the same configuration.
An example:

# ./scripts/Build-Pkg -prefix /usr gcc=3Dgcc40
# ./scripts/Build-Pkg -prefix /usr gcc=3Dgcc40_again

This will cause the package gcc=3Dgcc40_again to fail because it shares fil=
es
with gcc=3Dgcc40.
You could, however, play around with the stages using the pkgfilter hook.
That way you could move the build-everything stage from 5 to, say, 7 and
build the compile toolchain several times in stages 2-6. Stage 2 is the fir=
st
one in the chroot environment which stages 0-1 set up.


Greetings,
	Benjamin
--=20
Benjamin 'blindCoder' Schieder
Registered Linux User #289529: http://counter.li.org
finger blindcoder-1k+CIuW/[email protected] | gpg --import
--=20
You're individual!
You're unique!
Just like everyone else!

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFVubiAsME5O4xgqgRAt4DAKCM5hMrnkASSTCtr1LHPaLMCZvFdgCfRTMn
GpMLqXUIT/rxeweR49kiYGU=
=FvVd
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--

--===============2114542523==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rock-devel mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-devel

--===============2114542523==--