-
Notifications
You must be signed in to change notification settings - Fork 269
/
README.pkgs_specs
226 lines (147 loc) · 6.95 KB
/
README.pkgs_specs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
#######################
EXAMPLE OF DISTRO_SPECS
#######################
DISTRO_NAME='Slacko Puppy'
DISTRO_VERSION=5.8.3
DISTRO_BINARY_COMPAT='slackware'
DISTRO_FILE_PREFIX='slacko'
DISTRO_COMPAT_VERSION='14.0'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14'
###########################
EXAMPLE OF DISTRO_PET_REPOS
###########################
PKG_DOCS_PET_REPOS="
z|https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE/testing/woof-distro/x86/${DISTRO_BINARY_COMPAT}/${DISTRO_DB_SUBNAME}/Packages-puppy-${DISTRO_DB_SUBNAME}-official|z
z|https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE/testing/woof-distro/Packages-puppy-noarch-official|z
z|https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE/testing/woof-distro/x86/Packages-puppy-common32-official|z
"
PET_REPOS="
z|http://distro.ibiblio.org/puppylinux|Packages-puppy-*-official
z|http://01micko.com/wdlkmpx/puppylinux|Packages-puppy-stretch-official
z|http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux|Packages-puppy-*-official
z|http://ftp.cc.uoc.gr/mirrors/linux/puppylinux|Packages-puppy-*-official
z|ftp://mirror.aarnet.edu.au/pub/puppylinux|Packages-puppy-*-official
"
PACKAGELISTS_PET_ORDER="
Packages-puppy-${DISTRO_DB_SUBNAME}-official
Packages-puppy-noarch-official
Packages-puppy-common32-official
"
#######################################
DISTRO_PKGS_SPECS-Distro-Distro_version
#######################################
Ex: DISTRO_PKGS_SPECS-debian-stretch
This file contains the pkgs specs..
PKGS_SPECS_TABLE
================
The $PKGS_SPECS_TABLE variable contains the pkg list to be used in the build,
however they be enabled or disabled.
yes|915resolution||exe,dev,doc,nls
no|aaa_elflibs|aaa_elflibs|exe,dev,doc,nls
You can also add comments
yes|eudev||exe,dev,doc,nls #note, requires kmod and a kernel with devtmpfs enabled.
SYNTAX
======
0 1 2 3
yes|expat|expat|exe,dev,doc,nls
(0) Yes/No. Yes = enabled. No = disabled.
(1) Generic name for pkg. Note: PET packages, if exist, use this name.
(2) Comma-separated list of compatible-distro pkg(s). '-' prefix, exclude.
Empty field, then use PET pkg. See below.
Must be exact name-only of pkg, else '*' on end is wildcard to search full name.
(3) How the package will get split up in woof (optional redirection '>' operator).
Missing field, it goes into exe. Can also redirect >null, means dump it.
PET OR COMPAT?
=============
0 1 2 3
yes|expat|expat|exe,dev,doc,nls
When you see (2) is not emtpy, it's usually a compat distro pkg
0 1 2 3
yes|expat||exe,dev,doc,nls
empty (2) usually means a pet pkg..
Except if you specify a pet repo at the end:
0 1 2 3 4!
yes|isomaster|isomaster|exe,dev,doc,nls|pet:tahr
( |pet:tahr = http://distro.ibiblio.org/puppylinux/pet_packages-tahr/ )
This is not encouraged, as its adds unnecesary complexity.
Please don't use it so I can simplify findpkgs...
DEPENDENCY RESOLUTION
=====================
0 1 2 3 4 5
yes|bluez|bluez,bluez-obexd|exe,dev,doc,nls||deps:yes
When you see deps:yes in (5), this activates automatic dependency resolution for this package.
Dependency resolution is implemented in support/resolvedeps.sh and recursively adds all unsatisfied dependencies of a package to the current package. For example, if bluez depends on libdw1, libical3, libbz2-1.0, libelf1 and libdb5.3, while libelf1 depends on zlib1g, and none of these packages are explicitly included in the build, the original entry in the package list is replaced with:
yes|bluez|bluez,bluez-obexd,libdw1,libical3,libbz2-1.0,libelf1,zlib1g,libdb5.3|exe,dev,doc,nls||deps:yes
Dependency resolution is performed only once, when findpkgs runs for the first time. Usually, this happens during 0setup.
COMPAT PKGS
===========
You can group packages (2) in the same generic name (1):
0 1 2 ..........
yes|poppler|libpoppler44,libpoppler-dev,poppler-utils,libpoppler-glib8,libpoppler-glib-dev|exe,dev,doc,nls
(2) Comma-separated list of compatible-distro pkg(s). '-' prefix, exclude.
Must be exact name-only of pkg, else '*' on end is wildcard to search full name.
EXE, DEV, DOC, NLS ?
==================
This is specially for 2createpackages
Let's clarify what EXE, DEV, DOC and NLS mean in the first place.
DEV = development files inside the pkg
DOC = documentation
NLS = locale files, native language support
EXE = everything else
You can see the results in the 'packages-$distro' dir
0 1 2 ...... 3
yes|xorg_base_new|appres,bdftopcf,......|exe,dev,doc,nls
split generic name (1) pkgs (2) into components... EXE, DEV, DOC, NLS
ex: (xenialpup)
packages-xenial/xorg_base_new
packages-xenial/xorg_base_new_DEV
packages-xenial/xorg_base_new_DOC
packages-xenial/xorg_base_new_NLS
If a pkg does not have a certain component the respective directory will not be
created.
EXE, DEV, DOC, NLS - II
==================
yes|expat||exe,dev
Split only EXE and DEV components
DOC and NLS go to EXE
yes|expat|expat|exe
Pkg will not be split. Everything will go to EXE.
EXE, DEV, DOC, NLS - '>'
==================
The redirection '>' operator let's you have more control. You can redirect..
Let's see some examples
yes|glibc_locales|glibc,glibc-zoneinfo,glibc-i18n|exe,dev,doc,nls>exe| #slackware glibc-i18n- does not have enough files, need to extract from full glibc...
Redirect NLS to EXE. NLS files will go in the main (exe) dir.
yes|apr|apr|exe>dev,dev,doc,nls
Split into exe, dev, doc, nls... but the EXE stuff goes in DEV
NULL
----
By redirecting to null (>null), the component will be ignored,
this basically speeds up processing..
yes|bc|bc|exe,dev>null,doc,nls
Ignore DEV component
yes|bash||exe,dev>null,doc>null,nls
Ignore DEV and DOC
Do you know any problematic compat pkg that shouldn't be installed
because it breaks puppy? Send all components to NULL.
yes|udev|udev,libudev1,libudev-dev|exe>null,dev>null,doc>null,nls>null #fake install
The udev pkg is specially problematic because it's the systemd crap.
So here we fake the installation of udev, libudev-1 and libudev-dev
The pkgs will appear to be installed and won't cause any problems
with dependencies in the PPM. It has been replaced by:
yes|eudev||exe,dev,doc,nls #pet pkg: replaces udev and libudev
3BUILDDISTRO
============
There is code in 3builddistro that deletes the unneeded DOC and NLS
components in the EXE (main) dir. This is to achieve a smaller iso.
This will go the main puppy SFS
packages-xenial/xorg_base_new
This will go the DEVX sfs
packages-xenial/xorg_base_new_DEV
These will not be processed
packages-xenial/xorg_base_new_DOC
packages-xenial/xorg_base_new_NLS
(however you can use those dirs for your own purposes or script)
---
END