wok-next rev 21165
Update proot
| author | Aleksej Bobylev <al.bobylev@gmail.com> |
|---|---|
| date | Sat Mar 23 12:48:28 2019 +0200 (2019-03-23) |
| parents | 9a2b4a8379d5 |
| children | 06f83e7bab65 |
| files | gdbm/receipt libxfontcache/receipt proot/.icon.png proot/receipt proot/stuff/patches/man.patch proot/stuff/patches/series tazpkg/receipt xf86-video-dummy/stuff/patches/mibstore.patch xf86-video-dummy/stuff/patches/series |
line diff
1.1 --- a/gdbm/receipt Thu Feb 28 10:34:08 2019 +0100 1.2 +++ b/gdbm/receipt Sat Mar 23 12:48:28 2019 +0200 1.3 @@ -6,7 +6,7 @@ 1.4 SHORT_DESC="GNU database manager" 1.5 MAINTAINER="pascal.bellard@slitaz.org" 1.6 LICENSE="GPL3" 1.7 -WEB_SITE="https://www.gnu.org/software/gdbm/" # How to avoid redirection to local GNU mirror? 1.8 +WEB_SITE="https://www.gnu.org.ua/software/gdbm/" 1.9 LFS="http://www.linuxfromscratch.org/lfs/view/development/chapter06/gdbm.html" 1.10 1.11 TARBALL="$PACKAGE-$VERSION.tar.gz"
2.1 --- a/libxfontcache/receipt Thu Feb 28 10:34:08 2019 +0100 2.2 +++ b/libxfontcache/receipt Sat Mar 23 12:48:28 2019 +0200 2.3 @@ -16,7 +16,7 @@ 2.4 SPLIT="$PACKAGE-dev" 2.5 2.6 DEPENDS_std="libx11 libxext" 2.7 -DEPENDS="$PACKAGE xorgproto libx11-dev libxext-dev" 2.8 +DEPENDS_dev="$PACKAGE xorgproto libx11-dev libxext-dev" 2.9 2.10 compile_rules() { 2.11 ./configure \
3.1 Binary file proot/.icon.png has changed
4.1 --- a/proot/receipt Thu Feb 28 10:34:08 2019 +0100 4.2 +++ b/proot/receipt Sat Mar 23 12:48:28 2019 +0200 4.3 @@ -1,25 +1,24 @@ 4.4 # SliTaz package receipt v2. 4.5 4.6 PACKAGE="proot" 4.7 -VERSION="3.2.2" 4.8 +VERSION="5.1.0" 4.9 CATEGORY="misc" 4.10 SHORT_DESC="User-space implementation of chroot, mount --bind, and binfmt_misc" 4.11 MAINTAINER="pascal.bellard@slitaz.org" 4.12 LICENSE="GPL2" 4.13 -WEB_SITE="http://proot.me/" 4.14 +WEB_SITE="https://proot-me.github.io/" 4.15 4.16 TARBALL="$PACKAGE-$VERSION.tar.gz" 4.17 -WGET_URL="https://github.com/cedric-vincent/PRoot/archive/v$VERSION.tar.gz" 4.18 +WGET_URL="https://github.com/proot-me/PRoot/archive/v$VERSION.tar.gz" 4.19 4.20 BUILD_DEPENDS="talloc-dev" 4.21 4.22 compile_rules() { 4.23 cd $src/src 4.24 - make && 4.25 - install -Dm755 src/proot $install/usr/bin/proot 4.26 + make proot || return 1 4.27 + 4.28 + install -Dm755 proot $install/usr/bin/proot 4.29 + install -Dm644 $src/doc/proot/man.1 $install/usr/share/man/man1/proot.1 4.30 } 4.31 4.32 -genpkg_rules() { 4.33 - copy @std 4.34 - DEPENDS="talloc" 4.35 -} 4.36 +DEPENDS="talloc"
5.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 5.2 +++ b/proot/stuff/patches/man.patch Sat Mar 23 12:48:28 2019 +0200 5.3 @@ -0,0 +1,547 @@ 5.4 +--- a/doc/proot/man.1 5.5 ++++ b/doc/proot/man.1 5.6 +@@ -1,48 +1,19 @@ 5.7 +-.\" Man page generated from reStructuredText. 5.8 +-. 5.9 + .TH PROOT 1 "2014-12-12" "5.1.0" "" 5.10 + .SH NAME 5.11 +-PRoot \- chroot, mount --bind, and binfmt_misc without privilege/setup 5.12 +-. 5.13 +-.nr rst2man-indent-level 0 5.14 +-. 5.15 +-.de1 rstReportMargin 5.16 +-\\$1 \\n[an-margin] 5.17 +-level \\n[rst2man-indent-level] 5.18 +-level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] 5.19 +-- 5.20 +-\\n[rst2man-indent0] 5.21 +-\\n[rst2man-indent1] 5.22 +-\\n[rst2man-indent2] 5.23 +-.. 5.24 +-.de1 INDENT 5.25 +-.\" .rstReportMargin pre: 5.26 +-. RS \\$1 5.27 +-. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin] 5.28 +-. nr rst2man-indent-level +1 5.29 +-.\" .rstReportMargin post: 5.30 +-.. 5.31 +-.de UNINDENT 5.32 +-. RE 5.33 +-.\" indent \\n[an-margin] 5.34 +-.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]] 5.35 +-.nr rst2man-indent-level -1 5.36 +-.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] 5.37 +-.in \\n[rst2man-indent\\n[rst2man-indent-level]]u 5.38 +-.. 5.39 ++PRoot \- chroot, mount \-\-bind, and binfmt_misc without privilege/setup 5.40 + .SH SYNOPSIS 5.41 + .sp 5.42 + \fBproot\fP [\fIoption\fP] ... [\fIcommand\fP] 5.43 + .SH DESCRIPTION 5.44 + .sp 5.45 + PRoot is a user\-space implementation of \fBchroot\fP, \fBmount \-\-bind\fP, 5.46 +-and \fBbinfmt_misc\fP\&. This means that users don\(aqt need any privileges 5.47 ++and \fBbinfmt_misc\fP\&. This means that users don't need any privileges 5.48 + or setup to do things like using an arbitrary directory as the new 5.49 + root filesystem, making files accessible somewhere else in the 5.50 + filesystem hierarchy, or executing programs built for another CPU 5.51 + architecture transparently through QEMU user\-mode. Also, developers 5.52 + can use PRoot as a generic Linux process instrumentation engine thanks 5.53 +-to its extension mechanism, see \fI\%CARE\fP for an example. Technically 5.54 ++to its extension mechanism, see \fICARE\fP for an example. Technically 5.55 + PRoot relies on \fBptrace\fP, an unprivileged system\-call available in 5.56 + every Linux kernel. 5.57 + .sp 5.58 +@@ -55,9 +26,9 @@ 5.59 + .sp 5.60 + When the guest Linux distribution is made for a CPU architecture 5.61 + incompatible with the host one, PRoot uses the CPU emulator QEMU 5.62 +-user\-mode to execute transparently guest programs. It\(aqs a convenient 5.63 ++user\-mode to execute transparently guest programs. It's a convenient 5.64 + way to develop, to build, and to validate any guest Linux packages 5.65 +-seamlessly on users\(aq computer, just as if they were in a \fInative\fP 5.66 ++seamlessly on users' computer, just as if they were in a \fInative\fP 5.67 + guest environment. That way all of the cross\-compilation issues are 5.68 + avoided. 5.69 + .sp 5.70 +@@ -75,12 +46,11 @@ 5.71 + if they were "normal" host programs. 5.72 + .SH OPTIONS 5.73 + .sp 5.74 +-The command\-line interface is composed of two parts: first PRoot\(aqs 5.75 ++The command\-line interface is composed of two parts: first PRoot's 5.76 + options (optional), then the command to launch (\fB/bin/sh\fP if not 5.77 + specified). This section describes the options supported by PRoot, 5.78 + that is, the first part of its command\-line interface. 5.79 + .SS Regular options 5.80 +-.INDENT 0.0 5.81 + .TP 5.82 + .BI \-r \ path\fP,\fB \ \-\-rootfs\fB= path 5.83 + Use \fIpath\fP as the new guest root file\-system, default is \fB/\fP\&. 5.84 +@@ -104,7 +74,7 @@ 5.85 + guest location is a symbolic link, it is dereferenced to ensure 5.86 + the new content is accessible through all the symbolic links that 5.87 + point to the overlaid content. In most cases this default 5.88 +-behavior shouldn\(aqt be a problem, although it is possible to 5.89 ++behavior shouldn't be a problem, although it is possible to 5.90 + explicitly not dereference the guest location by appending it the 5.91 + \fB!\fP character: \fB\-b *host_path*:*guest_location!*\fP\&. 5.92 + .TP 5.93 +@@ -137,14 +107,12 @@ 5.94 + .TP 5.95 + .B \-h\fP,\fB \-\-help\fP,\fB \-\-usage 5.96 + Print the version and the command\-line usage, then exit. 5.97 +-.UNINDENT 5.98 + .SS Extension options 5.99 + .sp 5.100 + The following options enable built\-in extensions. Technically 5.101 + developers can add their own features to PRoot or use it as a Linux 5.102 + process instrumentation engine thanks to its extension mechanism, see 5.103 + the sources for further details. 5.104 +-.INDENT 0.0 5.105 + .TP 5.106 + .BI \-k \ string\fP,\fB \ \-\-kernel\-release\fB= string 5.107 + Make current kernel appear as kernel release \fIstring\fP\&. 5.108 +@@ -174,11 +142,9 @@ 5.109 + \fIgid\fP\&. Likewise, files actually owned by the current user and 5.110 + group appear as if they were owned by \fIuid\fP and \fIgid\fP instead. 5.111 + Note that the \fB\-0\fP option is the same as \fB\-i 0:0\fP\&. 5.112 +-.UNINDENT 5.113 + .SS Alias options 5.114 + .sp 5.115 + The following options are aliases for handy sets of options. 5.116 +-.INDENT 0.0 5.117 + .TP 5.118 + .BI \-R \ path 5.119 + Alias: \fB\-r *path*\fP + a couple of recommended \fB\-b\fP\&. 5.120 +@@ -187,10 +153,9 @@ 5.121 + access information about the host system, as it is illustrated in 5.122 + the \fBExamples\fP section of the manual. These host information 5.123 + are typically: user/group definition, network setup, run\-time 5.124 +-information, users\(aq files, ... On all Linux distributions, they 5.125 ++information, users' files, ... On all Linux distributions, they 5.126 + all lie in a couple of host files and directories that are 5.127 + automatically bound by this option: 5.128 +-.INDENT 7.0 5.129 + .IP \(bu 2 5.130 + /etc/host.conf 5.131 + .IP \(bu 2 5.132 +@@ -229,7 +194,6 @@ 5.133 + $HOME 5.134 + .IP \(bu 2 5.135 + \fIpath\fP 5.136 +-.UNINDENT 5.137 + .TP 5.138 + .BI \-S \ path 5.139 + Alias: \fB\-0 \-r *path*\fP + a couple of recommended \fB\-b\fP\&. 5.140 +@@ -238,7 +202,6 @@ 5.141 + the guest rootfs. It is similar to the \fB\-R\fP option expect it 5.142 + enables the \fB\-0\fP option and binds only the following minimal set 5.143 + of paths to avoid unexpected changes on host files: 5.144 +-.INDENT 7.0 5.145 + .IP \(bu 2 5.146 + /etc/host.conf 5.147 + .IP \(bu 2 5.148 +@@ -261,8 +224,6 @@ 5.149 + $HOME 5.150 + .IP \(bu 2 5.151 + \fIpath\fP 5.152 +-.UNINDENT 5.153 +-.UNINDENT 5.154 + .SH EXIT STATUS 5.155 + .sp 5.156 + If an internal error occurs, \fBproot\fP returns a non\-zero exit status, 5.157 +@@ -285,8 +246,6 @@ 5.158 + \fBproot\fP the path to the guest rootfs followed by the desired 5.159 + command. The example below executes the program \fBcat\fP to print the 5.160 + content of a file: 5.161 +-.INDENT 0.0 5.162 +-.INDENT 3.5 5.163 + .sp 5.164 + .nf 5.165 + .ft C 5.166 +@@ -295,14 +254,10 @@ 5.167 + Welcome to Slackware Linux 8.0 5.168 + .ft P 5.169 + .fi 5.170 +-.UNINDENT 5.171 +-.UNINDENT 5.172 + .sp 5.173 + The default command is \fB/bin/sh\fP when none is specified. Thus the 5.174 + shortest way to confine an interactive shell and all its sub\-programs 5.175 + is: 5.176 +-.INDENT 0.0 5.177 +-.INDENT 3.5 5.178 + .sp 5.179 + .nf 5.180 + .ft C 5.181 +@@ -312,15 +267,11 @@ 5.182 + Welcome to Slackware Linux 8.0 5.183 + .ft P 5.184 + .fi 5.185 +-.UNINDENT 5.186 +-.UNINDENT 5.187 + .SS \fBmount \-\-bind\fP equivalent 5.188 + .sp 5.189 + The bind mechanism enables one to relocate files and directories. This is 5.190 + typically useful to trick programs that perform access to hard\-coded 5.191 + locations, like some installation scripts: 5.192 +-.INDENT 0.0 5.193 +-.INDENT 3.5 5.194 + .sp 5.195 + .nf 5.196 + .ft C 5.197 +@@ -333,14 +284,10 @@ 5.198 + [...] # prog is installed in "/tmp/alternate_opt/bin" actually 5.199 + .ft P 5.200 + .fi 5.201 +-.UNINDENT 5.202 +-.UNINDENT 5.203 + .sp 5.204 + As shown in this example, it is possible to bind over files not even 5.205 + owned by the user. This can be used to \fIoverlay\fP system configuration 5.206 + files, for instance the DNS setting: 5.207 +-.INDENT 0.0 5.208 +-.INDENT 3.5 5.209 + .sp 5.210 + .nf 5.211 + .ft C 5.212 +@@ -348,25 +295,19 @@ 5.213 + \-rw\-r\-\-r\-\- 1 root root 675 Mar 4 2011 /etc/hosts 5.214 + .ft P 5.215 + .fi 5.216 +-.UNINDENT 5.217 +-.UNINDENT 5.218 +-.INDENT 0.0 5.219 +-.INDENT 3.5 5.220 + .sp 5.221 + .nf 5.222 + .ft C 5.223 + proot \-b ~/alternate_hosts:/etc/hosts 5.224 + 5.225 +-$ echo \(aq1.2.3.4 google.com\(aq > /etc/hosts 5.226 ++$ echo '1.2.3.4 google.com' > /etc/hosts 5.227 + $ resolveip google.com 5.228 + IP address of google.com is 1.2.3.4 5.229 +-$ echo \(aq5.6.7.8 google.com\(aq > /etc/hosts 5.230 ++$ echo '5.6.7.8 google.com' > /etc/hosts 5.231 + $ resolveip google.com 5.232 + IP address of google.com is 5.6.7.8 5.233 + .ft P 5.234 + .fi 5.235 +-.UNINDENT 5.236 +-.UNINDENT 5.237 + .sp 5.238 + Another example: on most Linux distributions \fB/bin/sh\fP is a symbolic 5.239 + link to \fB/bin/bash\fP, whereas it points to \fB/bin/dash\fP on Debian 5.240 +@@ -374,21 +315,15 @@ 5.241 + might not work with Dash. In this case, the binding mechanism of 5.242 + PRoot can be used to set non\-disruptively \fB/bin/bash\fP as the default 5.243 + \fB/bin/sh\fP on these two Linux distributions: 5.244 +-.INDENT 0.0 5.245 +-.INDENT 3.5 5.246 + .sp 5.247 + .nf 5.248 + .ft C 5.249 + proot \-b /bin/bash:/bin/sh [...] 5.250 + .ft P 5.251 + .fi 5.252 +-.UNINDENT 5.253 +-.UNINDENT 5.254 + .sp 5.255 + Because \fB/bin/sh\fP is initially a symbolic link to \fB/bin/dash\fP, the 5.256 + content of \fB/bin/bash\fP is actually bound over this latter: 5.257 +-.INDENT 0.0 5.258 +-.INDENT 3.5 5.259 + .sp 5.260 + .nf 5.261 + .ft C 5.262 +@@ -402,18 +337,14 @@ 5.263 + 089ed56cd74e63f461bef0fdfc2d159a /bin/dash 5.264 + .ft P 5.265 + .fi 5.266 +-.UNINDENT 5.267 +-.UNINDENT 5.268 + .sp 5.269 +-In most cases this shouldn\(aqt be a problem, but it is still possible to 5.270 ++In most cases this shouldn't be a problem, but it is still possible to 5.271 + strictly bind \fB/bin/bash\fP over \fB/bin/sh\fP \-\- without dereferencing 5.272 + it \-\- by specifying the \fB!\fP character at the end: 5.273 +-.INDENT 0.0 5.274 +-.INDENT 3.5 5.275 + .sp 5.276 + .nf 5.277 + .ft C 5.278 +-proot \-b \(aq/bin/bash:/bin/sh!\(aq 5.279 ++proot \-b '/bin/bash:/bin/sh!' 5.280 + 5.281 + $ md5sum /bin/sh 5.282 + 089ed56cd74e63f461bef0fdfc2d159a /bin/sh 5.283 +@@ -423,16 +354,12 @@ 5.284 + c229085928dc19e8d9bd29fe88268504 /bin/dash 5.285 + .ft P 5.286 + .fi 5.287 +-.UNINDENT 5.288 +-.UNINDENT 5.289 + .SS \fBchroot\fP + \fBmount \-\-bind\fP equivalent 5.290 + .sp 5.291 + The two features above can be combined to make any file from the host 5.292 + rootfs accessible in the confined environment just as if it were 5.293 + initially part of the guest rootfs. It is sometimes required to run 5.294 + programs that rely on some specific files: 5.295 +-.INDENT 0.0 5.296 +-.INDENT 3.5 5.297 + .sp 5.298 + .nf 5.299 + .ft C 5.300 +@@ -442,12 +369,8 @@ 5.301 + Error, do this: mount \-t proc none /proc 5.302 + .ft P 5.303 + .fi 5.304 +-.UNINDENT 5.305 +-.UNINDENT 5.306 + .sp 5.307 + works better with: 5.308 +-.INDENT 0.0 5.309 +-.INDENT 3.5 5.310 + .sp 5.311 + .nf 5.312 + .ft C 5.313 +@@ -461,14 +384,10 @@ 5.314 + ? ps \-o tty,command 5.315 + .ft P 5.316 + .fi 5.317 +-.UNINDENT 5.318 +-.UNINDENT 5.319 + .sp 5.320 +-Actually there\(aqs a bunch of such specific files, that\(aqs why PRoot 5.321 ++Actually there's a bunch of such specific files, that's why PRoot 5.322 + provides the option \fB\-R\fP to bind automatically a pre\-defined list of 5.323 + recommended paths: 5.324 +-.INDENT 0.0 5.325 +-.INDENT 3.5 5.326 + .sp 5.327 + .nf 5.328 + .ft C 5.329 +@@ -482,16 +401,12 @@ 5.330 + pts/6 ps \-o tty,command 5.331 + .ft P 5.332 + .fi 5.333 +-.UNINDENT 5.334 +-.UNINDENT 5.335 + .SS \fBchroot\fP + \fBmount \-\-bind\fP + \fBsu\fP equivalent 5.336 + .sp 5.337 + Some programs will not work correctly if they are not run by the 5.338 + "root" user, this is typically the case with package managers. PRoot 5.339 + can fake the root identity and its privileges when the \fB\-0\fP (zero) 5.340 + option is specified: 5.341 +-.INDENT 0.0 5.342 +-.INDENT 3.5 5.343 + .sp 5.344 + .nf 5.345 + .ft C 5.346 +@@ -502,13 +417,11 @@ 5.347 + 5.348 + # mkdir /tmp/foo 5.349 + # chmod a\-rwx /tmp/foo 5.350 +-# echo \(aqI bypass file\-system permissions.\(aq > /tmp/foo/bar 5.351 ++# echo 'I bypass file\-system permissions.' > /tmp/foo/bar 5.352 + # cat /tmp/foo/bar 5.353 + I bypass file\-system permissions. 5.354 + .ft P 5.355 + .fi 5.356 +-.UNINDENT 5.357 +-.UNINDENT 5.358 + .sp 5.359 + This option is typically required to create or install packages into 5.360 + the guest rootfs. Note it is \fInot\fP recommended to use the \fB\-R\fP 5.361 +@@ -516,8 +429,6 @@ 5.362 + system files, like \fB/etc/group\fP\&. Instead, it is recommended to use 5.363 + the \fB\-S\fP option. This latter enables the \fB\-0\fP option and binds 5.364 + only paths that are known to not be updated by packages: 5.365 +-.INDENT 0.0 5.366 +-.INDENT 3.5 5.367 + .sp 5.368 + .nf 5.369 + .ft C 5.370 +@@ -527,18 +438,14 @@ 5.371 + Installing package perl... 5.372 + .ft P 5.373 + .fi 5.374 +-.UNINDENT 5.375 +-.UNINDENT 5.376 + .SS \fBchroot\fP + \fBmount \-\-bind\fP + \fBbinfmt_misc\fP equivalent 5.377 + .sp 5.378 + PRoot uses QEMU user\-mode to execute programs built for a CPU 5.379 +-architecture incompatible with the host one. From users\(aq 5.380 ++architecture incompatible with the host one. From users' 5.381 + point\-of\-view, guest programs handled by QEMU user\-mode are executed 5.382 + transparently, that is, just like host programs. To enable this 5.383 + feature users just have to specify which instance of QEMU user\-mode 5.384 + they want to use with the option \fB\-q\fP: 5.385 +-.INDENT 0.0 5.386 +-.INDENT 3.5 5.387 + .sp 5.388 + .nf 5.389 + .ft C 5.390 +@@ -548,31 +455,23 @@ 5.391 + Welcome to ARMedSlack Linux 12.2 5.392 + .ft P 5.393 + .fi 5.394 +-.UNINDENT 5.395 +-.UNINDENT 5.396 + .sp 5.397 + The parameter of the \fB\-q\fP option is actually a whole QEMU user\-mode 5.398 + command, for instance to enable its GDB server on port 1234: 5.399 +-.INDENT 0.0 5.400 +-.INDENT 3.5 5.401 + .sp 5.402 + .nf 5.403 + .ft C 5.404 + proot \-R /mnt/armslack\-12.2/ \-q "qemu\-arm \-g 1234" emacs 5.405 + .ft P 5.406 + .fi 5.407 +-.UNINDENT 5.408 +-.UNINDENT 5.409 + .sp 5.410 + PRoot allows one to mix transparently the emulated execution of guest 5.411 + programs and the native execution of host programs in the same 5.412 +-file\-system namespace. It\(aqs typically useful to extend the list of 5.413 ++file\-system namespace. It's typically useful to extend the list of 5.414 + available programs and to speed up build\-time significantly. This 5.415 + mixed\-execution feature is enabled by default when using QEMU 5.416 + user\-mode, and the content of the host rootfs is made accessible 5.417 + through \fB/host\-rootfs\fP: 5.418 +-.INDENT 0.0 5.419 +-.INDENT 3.5 5.420 + .sp 5.421 + .nf 5.422 + .ft C 5.423 +@@ -580,24 +479,20 @@ 5.424 + 5.425 + $ file /bin/echo 5.426 + [...] ELF 32\-bit LSB executable, ARM [...] 5.427 +-$ /bin/echo \(aqHello world!\(aq 5.428 ++$ /bin/echo 'Hello world!' 5.429 + Hello world! 5.430 + 5.431 + $ file /host\-rootfs/bin/echo 5.432 + [...] ELF 64\-bit LSB executable, x86\-64 [...] 5.433 +-$ /host\-rootfs/bin/echo \(aqHello mixed world!\(aq 5.434 ++$ /host\-rootfs/bin/echo 'Hello mixed world!' 5.435 + Hello mixed world! 5.436 + .ft P 5.437 + .fi 5.438 +-.UNINDENT 5.439 +-.UNINDENT 5.440 + .sp 5.441 + Since both host and guest programs use the guest rootfs as \fB/\fP, 5.442 + users may want to deactivate explicitly cross\-filesystem support found 5.443 + in most GNU cross\-compilation tools. For example with GCC configured 5.444 + to cross\-compile to the ARM target: 5.445 +-.INDENT 0.0 5.446 +-.INDENT 3.5 5.447 + .sp 5.448 + .nf 5.449 + .ft C 5.450 +@@ -608,14 +503,10 @@ 5.451 + $ ./configure; make 5.452 + .ft P 5.453 + .fi 5.454 +-.UNINDENT 5.455 +-.UNINDENT 5.456 + .sp 5.457 + As with regular files, a host instance of a program can be bound over 5.458 + its guest instance. Here is an example where the guest binary of 5.459 + \fBmake\fP is overlaid by the host one: 5.460 +-.INDENT 0.0 5.461 +-.INDENT 3.5 5.462 + .sp 5.463 + .nf 5.464 + .ft C 5.465 +@@ -628,31 +519,24 @@ 5.466 + Built for x86_64\-slackware\-linux\-gnu 5.467 + .ft P 5.468 + .fi 5.469 +-.UNINDENT 5.470 +-.UNINDENT 5.471 + .sp 5.472 +-It\(aqs worth mentioning that even when mixing the native execution of 5.473 ++It's worth mentioning that even when mixing the native execution of 5.474 + host programs and the emulated execution of guest programs, they still 5.475 + believe they are running in a native guest environment. As a 5.476 + demonstration, here is a partial output of a typical \fB\&./configure\fP 5.477 + script: 5.478 +-.INDENT 0.0 5.479 +-.INDENT 3.5 5.480 + .sp 5.481 + .nf 5.482 + .ft C 5.483 + checking whether the C compiler is a cross\-compiler... no 5.484 + .ft P 5.485 + .fi 5.486 +-.UNINDENT 5.487 +-.UNINDENT 5.488 + .SH DOWNLOADS 5.489 + .SS PRoot 5.490 + .sp 5.491 + The latest release of PRoot is packaged on \fI\%http://packages.proot.me\fP 5.492 + and sources are hosted on \fI\%http://github.proot.me\fP\&. It is also 5.493 + available as highly compatible static binaries: 5.494 +-.INDENT 0.0 5.495 + .IP \(bu 2 5.496 + for x86_64: \fI\%http://static.proot.me/proot\-x86_64\fP 5.497 + .IP \(bu 2 5.498 +@@ -661,14 +545,12 @@ 5.499 + for ARM: \fI\%http://static.proot.me/proot\-arm\fP 5.500 + .IP \(bu 2 5.501 + other architectures: on demand. 5.502 +-.UNINDENT 5.503 + .SS Rootfs 5.504 + .sp 5.505 + Here follows a couple of URLs where some rootfs archives can be freely 5.506 + downloaded. Note that \fBmknod\fP errors reported by \fBtar\fP when 5.507 + extracting these archives can be safely ignored since special files 5.508 + are typically bound (see \fB\-R\fP option for details). 5.509 +-.INDENT 0.0 5.510 + .IP \(bu 2 5.511 + \fI\%http://download.openvz.org/template/precreated/\fP 5.512 + .IP \(bu 2 5.513 +@@ -679,20 +561,15 @@ 5.514 + \fI\%http://cdimage.ubuntu.com/ubuntu\-core/releases/\fP 5.515 + .IP \(bu 2 5.516 + \fI\%http://archlinuxarm.org/developers/downloads\fP 5.517 +-.UNINDENT 5.518 + .sp 5.519 + Technically such rootfs archive can be created by running the 5.520 + following command on the expected Linux distribution: 5.521 +-.INDENT 0.0 5.522 +-.INDENT 3.5 5.523 + .sp 5.524 + .nf 5.525 + .ft C 5.526 + tar \-\-one\-file\-system \-\-create \-\-gzip \-\-file my_rootfs.tar.gz / 5.527 + .ft P 5.528 + .fi 5.529 +-.UNINDENT 5.530 +-.UNINDENT 5.531 + .SS QEMU user\-mode 5.532 + .sp 5.533 + QEMU user\-mode is required only if the guest rootfs was made for a CPU 5.534 +@@ -710,8 +587,6 @@ 5.535 + .sp 5.536 + Visit \fI\%http://proot.me\fP for help, bug reports, suggestions, patches, ... 5.537 + Copyright (C) 2014 STMicroelectronics, licensed under GPL v2 or later. 5.538 +-.INDENT 0.0 5.539 +-.INDENT 3.5 5.540 + .sp 5.541 + .nf 5.542 + .ft C 5.543 +@@ -721,7 +596,4 @@ 5.544 + |__| |__|__\e_____/\e_____/\e____| 5.545 + .ft P 5.546 + .fi 5.547 +-.UNINDENT 5.548 +-.UNINDENT 5.549 +-.\" Generated by docutils manpage writer. 5.550 + .
6.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 6.2 +++ b/proot/stuff/patches/series Sat Mar 23 12:48:28 2019 +0200 6.3 @@ -0,0 +1,1 @@ 6.4 +man.patch
7.1 --- a/tazpkg/receipt Thu Feb 28 10:34:08 2019 +0100 7.2 +++ b/tazpkg/receipt Sat Mar 23 12:48:28 2019 +0200 7.3 @@ -11,6 +11,7 @@ 7.4 7.5 TARBALL="$PACKAGE-$VERSION.tar.bz2" 7.6 WGET_URL="http://hg.slitaz.org/tazpkg/archive/$VERSION.tar.bz2" 7.7 +TARBALL_SHA1="fd6663657bfdc9317b99cfeebc166e08debdc5c4" 7.8 7.9 BUILD_DEPENDS="gettext-dev tidy-html5 libnotify-dev" 7.10
8.1 --- a/xf86-video-dummy/stuff/patches/mibstore.patch Thu Feb 28 10:34:08 2019 +0100 8.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 8.3 @@ -1,18 +0,0 @@ 8.4 ---- ./src/ark_driver.c.orig 2013-03-07 10:16:06.584081552 +0000 8.5 -+++ ./src/ark_driver.c 2013-03-07 10:16:23.270892075 +0000 8.6 -@@ -39,7 +39,6 @@ 8.7 - #include "compiler.h" 8.8 - #include "mipointer.h" 8.9 - #include "micmap.h" 8.10 --#include "mibstore.h" 8.11 - #include "fb.h" 8.12 - #include "ark.h" 8.13 - 8.14 -@@ -538,7 +537,6 @@ 8.15 - 8.16 - fbPictureInit (pScreen, 0, 0); 8.17 - 8.18 -- miInitializeBackingStore(pScreen); 8.19 - xf86SetBackingStore(pScreen); 8.20 - 8.21 - if (!pARK->NoAccel) {