You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.6 KiB
1.6 KiB
Making a tarinstall
Detailed creation process
- A temporary directory is created, from now it will be referred to as
tmp/
- Inside
tmp/
the structure is created (bin/
,lib/
,env
, etc.) - The file
tmp/id
gets written tmp/bin/
gets populated with the executables listed in thedeps
file- The binaries inside
tmp/bin/
get read and the list of shared libraries gets written toliblist
- The
liblist
file gets read and all the necessary libraries get downloaded and/or copied totmp/lib/
, thenliblist
gets deleted - The
tmp/env
gets generated - The
tmp/man/
andtmp/ext/
directories get populated with the right files - The checksum for the files inside
tmp
gets calculated and written totmp/checksum
- The
tmp
directory gets compressed as a tar archive - The decompressor and loader programs get applied to the tar archive
- The archive gets renamed
<id>.ti
and granted executable permission
The project's root directory structure
The project's root directory has to contain a subdirectory called tarinstall
which has to contain the following elements:
id
file: contains the id name of the programtype
file: contains the type of projectdeps
file: contains a list of the binary files that the program uses
Types of project
The type
file may contain one or more of these option separated by a newline
in order to determine which binaries/libraries to download or copy from the
system and in order to generate the right env
file.
This requirement may be removed in favour of automatic recognition.
- C (also the option for C++)
- python
- go
- perl