Hi Shawn,
On 08 Jan 2019, at 04:03, Shawn Anastasio <[email protected]> wrote:
> Hello all,
Welcome!
> I recently discovered the t2 project and decided to try it out in a VM on my
> IBM POWER9-based workstation. Using the t2-minimal-ppc64-r46697.iso
> installer, I was able to successfully install the distro without too much
> fuss.
>
> My question now is, how does package management work? I've been looking
> through the handbook and see that the `mine` utility can be used for binary
> packages and this seems to work fine, but I am currently interested in
> building packages from source. I see that a script named `Emerge-Pkg` is
> supposed to allow this, but it is not present on my installation. I also see
> that it is present in the t2-trunk svn repo, but I'm unclear on how this is
> supposed to integrate with my existing system.
>
> I have checked out the t2-trunk repository to my t2 installation and
> attempted to use the included Emerge-Pkg script, but it complains that I
> don't have a configuration. It is my understanding, however, that the
> configuration files are used to define targets for bootstrapping a new t2
> build, not for extending an existing one. Is it possible to instruct the
> script to use my existing system configuration?
>
> If anybody could explain the t2 package management system and how to properly
> build packages from source for an existing system, it would be greatly
> appreciated.
Apart from building embedded firmware images and such, T2 can be for the most
part be considered a source based distribution.
So you indeed would use scripts/Emerge-Pkg to build packages from source.
You run scripts/Config once to select your configuration, and you could best
copy the ISO one installed in /etc/SDE-CONFIG/ to config/default as a binary
compatible start. Maybe we should change the installer to do so.
The ISO uses mine to install the pre-compiled binary packages, or embedded
systems could do so if the developer / vendor of such system ships binary
updates.
You can also use mine -r to remove / uninstall packages build form source.
The installer meta data are simple text files in /var/adm/…
Emerge-Pkg dependency resolution is a bit crude, as we use automatic file
access tracking on build time, we should probably spend a little more extra
effort to flag optional dependencies for Emerge-Pkg to build less by default.
So you might often run Emerge-Pkg with -deps=none
And if you want to quickly build something on vintage hardware and not update
minter updates -missing-only.
Hope that is a comprehensive / quick first summary and helps you get started.
If you have more questions just let us know!
René
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
http://exactcode.com | http://exactscan.com | http://ocrkit.com |
http://t2-project.org | http://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
