ArchLinux packages manager for Porteus
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
[rolling update issue]
There were some troubles in update by acuiUpdate.
1. Mouse cursor didn't move after updating "libinput and xf86-input-libinput".
It was the cause that new version of "libinput and xf86-input-libinput" needs "libwacom" package.
Therefore, it was fixed by adding "libwacom".
2. The file manager pcmanfm couldn't be executed after updating libfm.
It was the cause that some libraries that are needed by pcmanfm are separated from "libfm" to "libfm-gtk2".
Therefore, it was fixed by adding "libfm-gtk2".
3. gnumeric locale didn't display after updating "gnumeric" package.
It was the cause that the locale data name of "gnumeric" includes version number.
example: "gnumeric-1.12.27.mo"
Therefore, it was fixed by replacing with the correct locale data from .sep module.
P.S.
I am afraid of the mis decision that Arcklinux packages are employed for Porteus live ISO.
There are something wrong.
The concept of Archlinux, especially rolling release, might not fit with the concept of Porteus live ISO.
Thanks.
There were some troubles in update by acuiUpdate.
1. Mouse cursor didn't move after updating "libinput and xf86-input-libinput".
It was the cause that new version of "libinput and xf86-input-libinput" needs "libwacom" package.
Therefore, it was fixed by adding "libwacom".
2. The file manager pcmanfm couldn't be executed after updating libfm.
It was the cause that some libraries that are needed by pcmanfm are separated from "libfm" to "libfm-gtk2".
Therefore, it was fixed by adding "libfm-gtk2".
3. gnumeric locale didn't display after updating "gnumeric" package.
It was the cause that the locale data name of "gnumeric" includes version number.
example: "gnumeric-1.12.27.mo"
Therefore, it was fixed by replacing with the correct locale data from .sep module.
P.S.
I am afraid of the mis decision that Arcklinux packages are employed for Porteus live ISO.
There are something wrong.
The concept of Archlinux, especially rolling release, might not fit with the concept of Porteus live ISO.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
1. "archspm" was updated to version 16.02.14-5.
Please refer to the top article of this thread.
http://forum.porteus.org/viewtopic.php? ... 997#p36687
2. "APorteus FVWM" was updated to v16.03.10.
Please refer to the 3rd article of this thread.
http://forum.porteus.org/viewtopic.php? ... 997#p36689
Thanks.
Please refer to the top article of this thread.
http://forum.porteus.org/viewtopic.php? ... 997#p36687
2. "APorteus FVWM" was updated to v16.03.10.
Please refer to the 3rd article of this thread.
http://forum.porteus.org/viewtopic.php? ... 997#p36689
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
(transaction for v16.03.10)
(1) 002-z.xorg.xzm was updated
upv16.03.12.tar (2.5 M)
http://www.mediafire.com/download/1kcpa ... .03.12.tar
* md5sum list is included in upv16.03.12.tar
[the problem that will be fixed with upv16.03.12.tar]
If "pavucontrol" doesn't be done, "Skype" has no sound.
[How to update]
An example is done
in self running (APorteus-FVWM-v16.03.10-i486/APorteus-FVWM-v16.03.10-x86_64.iso) environment.
32bit
64bit
Thanks.
(1) 002-z.xorg.xzm was updated
upv16.03.12.tar (2.5 M)
http://www.mediafire.com/download/1kcpa ... .03.12.tar
* md5sum list is included in upv16.03.12.tar
[the problem that will be fixed with upv16.03.12.tar]
If "pavucontrol" doesn't be done, "Skype" has no sound.
[How to update]
An example is done
in self running (APorteus-FVWM-v16.03.10-i486/APorteus-FVWM-v16.03.10-x86_64.iso) environment.
32bit
Code: Select all
% su
# dISO APorteus-FVWM-v16.03.10-i486
# tar -xf upv16.03.12.tar
# mv upv16.03.12/32/002-z.xorg.xzm APorteus-FVWM-v16.03.10-i486/porteus/base/.
# mkISO APorteus-FVWM-v16.03.10-i486
# rm -fr APorteus-FVWM-v16.03.10-i486 upv16.03.12
Code: Select all
% su
# dISO APorteus-FVWM-v16.03.10-x86_64.iso
# tar -xf upv16.03.12.tar
# mv upv16.03.12/64/002-z.xorg.xzm APorteus-FVWM-v16.03.10-x86_64.iso/porteus/base/.
# mkISO APorteus-FVWM-v16.03.10-x86_64.iso
# rm -fr APorteus-FVWM-v16.03.10-x86_64.iso
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: ArchLinux packages manager for Porteus
Hello neko.
Should I understand that you have made some kind of nemesis version with APorteus-mini-v16.03.10-i486.iso?
Thanks.
Should I understand that you have made some kind of nemesis version with APorteus-mini-v16.03.10-i486.iso?
Thanks.
Prendre son temps, profiter de celui qui passe.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
@francois
No, you should not understand so.
APorteus was generated from archlinux-2015.10.01-dual.iso.
And it was reflected the result of "Sensei-v3.1-x86_64-2.iso and porteus-nemesis-v3.2-x86_64.iso"
Nemesis employs the "sysvinit style systemd".
And it's package management is based on pacman.
But APorteus employs the "systemd".
And it's package management is the archspm ( the Simple Package Manager for ArchLinux packages) not based on pacman.
Nemesis intends to release officially.
But, APorteus is trial to use Archlinux packages in Porteus frame.
It is sample to study "Archlinux & systemd" within Porteus frame.
Therefor some analyzing tools are opened.
Everybody can modify it by himself and create his own ISO.
Thanks.
No, you should not understand so.
APorteus was generated from archlinux-2015.10.01-dual.iso.
And it was reflected the result of "Sensei-v3.1-x86_64-2.iso and porteus-nemesis-v3.2-x86_64.iso"
Nemesis employs the "sysvinit style systemd".
And it's package management is based on pacman.
But APorteus employs the "systemd".
And it's package management is the archspm ( the Simple Package Manager for ArchLinux packages) not based on pacman.
Nemesis intends to release officially.
But, APorteus is trial to use Archlinux packages in Porteus frame.
It is sample to study "Archlinux & systemd" within Porteus frame.
Therefor some analyzing tools are opened.
Everybody can modify it by himself and create his own ISO.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
-- maintenance: basic library addition --
When a basic library may be need, it will be added into 001-core.xzm module.
[Add "GNU m4" package to ISO]
In self running (APorteus-FVWM-v16.03.10-i486/APorteus-FVWM-v16.03.10-x86_64.iso) environment.
1. get the package with GUI "archspm".
m4-1.4.17-i686-1.xzm/m4-1.4.17-x86_64-1.xzm
2. disassemble ISO and then XZM, merge, assemble.
example: 32bit
Thanks.
When a basic library may be need, it will be added into 001-core.xzm module.
[Add "GNU m4" package to ISO]
In self running (APorteus-FVWM-v16.03.10-i486/APorteus-FVWM-v16.03.10-x86_64.iso) environment.
1. get the package with GUI "archspm".
m4-1.4.17-i686-1.xzm/m4-1.4.17-x86_64-1.xzm
2. disassemble ISO and then XZM, merge, assemble.
example: 32bit
Code: Select all
% su
# ls -1
APorteus-mini-v16.03.10-i486.iso
m4-1.4.17-i686-1.xzm
# dISO APorteus-mini-v16.03.10-i486.iso
# dXZM APorteus-FVWM-v16.03.10-i486/porteus/base/001-core.xzm
# sep2pkg 001-core
# cd pkgs.001-core
# dXZM ../m4-1.4.17-i686-1.xzm
# cd ../
# mergepkgs pkgs.001-core
# mkXZM 001-core
# mv 001-core.xzm APorteus-FVWM-v16.03.10-i486/porteus/base/.
# mkISO APorteus-FVWM-v16.03.10-i486
# rm -fr APorteus-FVWM-v16.03.10-i486 001-core pkgs.001-core
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
--- add-on commands are updated ---
The commands offered in "mkslimjet" module,
http://forum.porteus.org/viewtopic.php? ... 875#p35562 ,
are modified and are included in "APorteus ISO" as add-on command.
Now, they are updated and are offered in "amkslimjet" module.
amkslimjet-16.03.13-noarch-1.xzm (127 K)
http://www.mediafire.com/download/ay4j8 ... arch-1.xzm
md5sum: 2258c9cc9e8a259c575c8eb460314b91 amkslimjet-16.03.13-noarch-1.xzm
[How to update]
32bit example is done
in self running (APorteus-FVWM-v16.03.10-i486.iso) environment.
(note) updated items.
1. delete slackware libraries for Porteus V3.1.
2. change the 64bit library directory from "lib64" to "lib".
3. convert a flash plug-in to xzm package merged with MPV plug-in.
Thanks.
The commands offered in "mkslimjet" module,
http://forum.porteus.org/viewtopic.php? ... 875#p35562 ,
are modified and are included in "APorteus ISO" as add-on command.
Now, they are updated and are offered in "amkslimjet" module.
amkslimjet-16.03.13-noarch-1.xzm (127 K)
http://www.mediafire.com/download/ay4j8 ... arch-1.xzm
md5sum: 2258c9cc9e8a259c575c8eb460314b91 amkslimjet-16.03.13-noarch-1.xzm
[How to update]
32bit example is done
in self running (APorteus-FVWM-v16.03.10-i486.iso) environment.
Code: Select all
% su
# ls -1
APorteus-FVWM-v16.03.10-i486.iso
amkslimjet-16.03.13-noarch-1.xzm
# dISO APorteus-FVWM-v16.03.10-i486.iso
# dXZM APorteus-FVWM-v16.03.10-i486/porteus/base/003-z.fvwm.xzm
# sep2pkg 003-z.fvwm
# cd pkgs.003-z.fvwm/pkg.spm/
# rm -fr mkslimjet-v3.1-noarch-9
# dXZM ../../amkslimjet-16.03.13-noarch-1.xzm
# cd ../../
# mergepkgs pkgs.003-z.fvwm; mkXZM 003-z.fvwm; rm -fr 003-z.fvwm pkgs.003-z.fvwm
# mv 003-z.fvwm.xzm APorteus-FVWM-v16.03.10-i486/porteus/base/.
# mkISO APorteus-FVWM-v16.03.10-i486; rm -fr APorteus-FVWM-v16.03.10-i486
1. delete slackware libraries for Porteus V3.1.
2. change the 64bit library directory from "lib64" to "lib".
3. convert a flash plug-in to xzm package merged with MPV plug-in.
Thanks.
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: ArchLinux packages manager for Porteus
Hello neko.
The APorteus-mini-v16.03.10-x86_64.iso will not boot under virtualbox.
Does it work for you?
Thanks.
The APorteus-mini-v16.03.10-x86_64.iso will not boot under virtualbox.
Does it work for you?
Thanks.
Prendre son temps, profiter de celui qui passe.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
@francois
I am sorry that Aporteus would not run under virtualbox.
I don't understand well about a virtualbox.
I have not experience to use a virtualbox yet.
And then I didn't care the virtualbox at all.
Would you tell me how to use a virtualbox of Porteus-KDE4-v3.1-x86_64.iso to boot Aporteus on it.
Then I will try it as follow your instructions.
Thanks.
I am sorry that Aporteus would not run under virtualbox.
I don't understand well about a virtualbox.
I have not experience to use a virtualbox yet.
And then I didn't care the virtualbox at all.
Would you tell me how to use a virtualbox of Porteus-KDE4-v3.1-x86_64.iso to boot Aporteus on it.
Then I will try it as follow your instructions.
Thanks.
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: ArchLinux packages manager for Porteus
You can build the vbox module with the virtual box builder in the system section of the panel menu.
Once virtual box is activated and started just click the new icon at left of the settings icon, type linux, version other linux, triple the size of the base memory to 1024 MB, select expandable hard disk drive, go for 16gig, OK.
Then selecting that virtual installation, select settings storage, select empty cd (and not vdi), at the right select the cd and go in the file system tree to select the aporteus.iso file.
Then start vbox and from cd gparted format the 16 gig hdd.
I am surprised you never used vbox. You will find it a wonderfull tool for the type of work you are doing.
Once virtual box is activated and started just click the new icon at left of the settings icon, type linux, version other linux, triple the size of the base memory to 1024 MB, select expandable hard disk drive, go for 16gig, OK.
Then selecting that virtual installation, select settings storage, select empty cd (and not vdi), at the right select the cd and go in the file system tree to select the aporteus.iso file.
Then start vbox and from cd gparted format the 16 gig hdd.
I am surprised you never used vbox. You will find it a wonderfull tool for the type of work you are doing.
Prendre son temps, profiter de celui qui passe.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
@francois
Thank you for your replay.
I tried as follow your instruction.
--->
But virtual box was not activated.
Then, I downloaded 05-devel.xzm and activated it.
Retry:
"the virtual box builder in the system section of the panel menu"
--->
But virtual box was not activated.
I understood that its usage is not so simple.
I will study on vbox.
Thanks.
P.S.
My PC skill is poor.
I don't have Windows OS.
For example, I don't have the experience to use Excel nor Word.
If I try to use complex PC matter, I should study it.
Thank you for your replay.
I tried as follow your instruction.
"the virtual box builder in the system section of the panel menu"You can build the vbox module with the virtual box builder in the system section of the panel menu.
Once virtual box is activated and ...
--->
But virtual box was not activated.
Then, I downloaded 05-devel.xzm and activated it.
Retry:
"the virtual box builder in the system section of the panel menu"
--->
But virtual box was not activated.
I understood that its usage is not so simple.
I will study on vbox.
Thanks.
P.S.
My PC skill is poor.
I don't have Windows OS.
For example, I don't have the experience to use Excel nor Word.
If I try to use complex PC matter, I should study it.
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: ArchLinux packages manager for Porteus
Neko do not say that. You really have great skills.
Once and a while the virtual box builder does not work.
Here is my vbox module for 64bit for porteus 3.1:
http://www.mediafire.com/download/p0qu4 ... 4-1prt.xzm
http://www.mediafire.com/download/skbey ... 4-1prt.xzm
Once and a while the virtual box builder does not work.
Here is my vbox module for 64bit for porteus 3.1:
http://www.mediafire.com/download/p0qu4 ... 4-1prt.xzm
http://www.mediafire.com/download/skbey ... 4-1prt.xzm
Prendre son temps, profiter de celui qui passe.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
@francois
Thank you for opening your vbox.
I downloaded they.
I will study.
Thanks.
P.S.
Everytime, my member ,who knows PC well, did set up my PC that was used as X-terminal only.
Therefore I lost the chance to get PC skill.
I have the experience to develop an embedded systems OS.
And I developed (Portable) C, assembler, linker, and debugger system for the embedded system under the UNIX environment.
I didn't answer exactly to your question about compile environment.
I have compiler knowledges a little. It made me hesitate to answer roughly.
I don't know it nor building environment well.
Those are more complex than Portable C for embedded that I did.
Thank you for opening your vbox.
I downloaded they.
I will study.
Thanks.
P.S.
Everytime, my member ,who knows PC well, did set up my PC that was used as X-terminal only.
Therefore I lost the chance to get PC skill.
I have the experience to develop an embedded systems OS.
And I developed (Portable) C, assembler, linker, and debugger system for the embedded system under the UNIX environment.
I didn't answer exactly to your question about compile environment.
I have compiler knowledges a little. It made me hesitate to answer roughly.
I don't know it nor building environment well.
Those are more complex than Portable C for embedded that I did.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
Porteus implements reducing the overall size by deleting the part of the package.
ArchSPM/APorteus leaves separates the part, which is this deleted at Porteus, as ".sep" module at APorteus.
This separation is done in accordance with the contents of the configuration file.
There are specified for the individual packages and for the entire package.
[ configuration of a package separation ]
A package is separated depending on the configuration data.
1. default configuration
/usr/local/share/archspm/lib/picks/sep/defaultDEL
2. pickup configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.pick
example:
imagemagick.pick is the pickup configuration for the imagemagick package.
3. delete configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.del
example:
fvwm.del is the delete configuration for the fvwm package.
4. recover configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.rec
This configuration must be defined with the pair of default configuration.
example:
glibc.rec is the recover configuration for glibc package.
(with glibc.del)
There are 4 patterns to separate.
Case 1: depending on pickup configuration.
example:
content of /usr/local/share/archspm/lib/picks/sep/imagemagick.pick
These directories/data are picked up from an original package,
and the rest are moved to ".sep"
Case 2: depending on delete configuration.
example:
content of /usr/local/share/archspm/lib/picks/sep/glibc.del
These directories/data and the content of /usr/local/share/archspm/lib/picks/sep/defaultDEL
are deleted from an original package and move to ".sep" package.
Case 3: depending on a pair of delete & recover configurations.
example:
content of /usr/local/share/archspm/lib/picks/sep/glibc.rec
First separation is done as case 2,
then the ".rec" content are move from ".sep" to the package.
Case 4: depending on only default configuration.
content of /usr/local/share/archspm/lib/picks/sep/defaultDEL
These directories are deleted from an original package and move to ".sep" package.
ArchSPM includes "defaultDEL" configuration file.
APortesu includes "defaultDEL" and some ".pick" , ".del" & ".rec" configuration files.
Thanks.
ArchSPM/APorteus leaves separates the part, which is this deleted at Porteus, as ".sep" module at APorteus.
This separation is done in accordance with the contents of the configuration file.
There are specified for the individual packages and for the entire package.
[ configuration of a package separation ]
A package is separated depending on the configuration data.
1. default configuration
/usr/local/share/archspm/lib/picks/sep/defaultDEL
2. pickup configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.pick
example:
imagemagick.pick is the pickup configuration for the imagemagick package.
3. delete configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.del
example:
fvwm.del is the delete configuration for the fvwm package.
4. recover configuration
/usr/local/share/archspm/lib/picks/sep/$PACKAGENAME.rec
This configuration must be defined with the pair of default configuration.
example:
glibc.rec is the recover configuration for glibc package.
(with glibc.del)
There are 4 patterns to separate.
Case 1: depending on pickup configuration.
example:
content of /usr/local/share/archspm/lib/picks/sep/imagemagick.pick
Code: Select all
/usr/bin/convert
/usr/lib/libMagickCore-6.Q16HDRI.so*
/usr/lib/libMagickWand-6.Q16HDRI.so*
/usr/lib/ImageMagick-*/modules-Q16HDRI/coders/jpeg.*
/usr/lib/ImageMagick-*/modules-Q16HDRI/coders/png.*
/usr/lib/ImageMagick-*/modules-Q16HDRI/coders/svg.*
and the rest are moved to ".sep"
Case 2: depending on delete configuration.
example:
content of /usr/local/share/archspm/lib/picks/sep/glibc.del
Code: Select all
/usr/share
/usr/lib/getconf
/usr/lib/gconv
are deleted from an original package and move to ".sep" package.
Case 3: depending on a pair of delete & recover configurations.
example:
content of /usr/local/share/archspm/lib/picks/sep/glibc.rec
Code: Select all
/usr/share/i18n/locales/en_US
/usr/share/i18n/charmaps/UTF-8.gz
/usr/share/i18n/charmaps/ANSI_X3.4-1968.gz
/usr/share/i18n/charmaps/ANSI_X3.110-1983.gz
/usr/share/i18n/charmaps/EUC-JISX0213.gz
/usr/share/i18n/charmaps/EUC-JP-MS.gz
/usr/share/i18n/charmaps/EUC-JP.gz
/usr/lib/getconf/XBS5_ILP32_OFF32
/usr/lib/getconf/POSIX_V6_ILP32_OFF32
/usr/lib/getconf/POSIX_V7_ILP32_OFF32
/usr/lib/gconv/ANSI_X3.110.so
/usr/lib/gconv/CP10007.so
/usr/lib/gconv/CP1125.so
/usr/lib/gconv/CP1250.so
/usr/lib/gconv/CP1251.so
/usr/lib/gconv/CP1252.so
/usr/lib/gconv/CP1253.so
/usr/lib/gconv/CP1254.so
/usr/lib/gconv/CP1255.so
/usr/lib/gconv/CP1256.so
/usr/lib/gconv/CP1257.so
/usr/lib/gconv/CP1258.so
/usr/lib/gconv/EUC-JISX0213.so
/usr/lib/gconv/EUC-JP-MS.so
/usr/lib/gconv/EUC-JP.so
/usr/lib/gconv/HP-ROMAN8.so
/usr/lib/gconv/HP-ROMAN9.so
/usr/lib/gconv/ISO8859-1.so
/usr/lib/gconv/UNICODE.so
/usr/lib/gconv/UTF-16.so
/usr/lib/gconv/UTF-32.so
/usr/lib/gconv/UTF-7.so
/usr/lib/gconv/libCNS.so
/usr/lib/gconv/libGB.so
/usr/lib/gconv/libISOIR165.so
/usr/lib/gconv/libJIS.so
/usr/lib/gconv/libJISX0213.so
/usr/lib/gconv/libKSC.so
/usr/lib/gconv/gconv-modules
then the ".rec" content are move from ".sep" to the package.
Case 4: depending on only default configuration.
content of /usr/local/share/archspm/lib/picks/sep/defaultDEL
Code: Select all
/usr/info
/usr/doc
/usr/man
/usr/src
/usr/include
/usr/lib/girepository-1.0
/usr/lib/pkgconfig
/usr/local/info
/usr/local/doc
/usr/local/man
/usr/share/aclocal
/usr/share/gtk-doc
/usr/share/info
/usr/share/doc
/usr/share/gir-1.0
/usr/share/man
/usr/share/licenses
/usr/share/locale
/usr/share/vala
ArchSPM includes "defaultDEL" configuration file.
APortesu includes "defaultDEL" and some ".pick" , ".del" & ".rec" configuration files.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Re: ArchLinux packages manager for Porteus
--- update man-page ---
First, a man-page package is treated as none-update package.
And its ".sep" module is included in ISO.
ISO@/porteus/modules/003-man-pages-4.04-noarch-1.sep.xzm
Now, it will be treated as updateable package.
The current version is man-pages-4.05-noarch-1.xzm.
Entity of manual are included man-pages-4.05-noarch-1.xzm.sep.
It can be changed by ".sep" configuration as following man-pages.pick.
man-pages.pick
About ".sep" configuration, please refer to http://forum.porteus.org/viewtopic.php? ... =30#p43335
step 1: add man-pages.pick to ".sep" configuration.
It is done
in self running (APorteus-FVWM-v16.03.10-i486.iso) environment.
example: 32bit
step 2: boot the ISO updated by step 1.
(case 1)
man-pages-4.05-noarch-1.xzm is already gotten in /YOURWORK.
Its separation must be changed depending on the new configuration.
In the another directory /X, it is done as following.
(case 2)
man-pages-4.05-noarch-1.xzm is not yet gotten.
Get it with GUI ArchAPM.
step 3: update man-pages of ISO
(continue from step 1,2)
Thanks.
First, a man-page package is treated as none-update package.
And its ".sep" module is included in ISO.
ISO@/porteus/modules/003-man-pages-4.04-noarch-1.sep.xzm
Now, it will be treated as updateable package.
The current version is man-pages-4.05-noarch-1.xzm.
Entity of manual are included man-pages-4.05-noarch-1.xzm.sep.
It can be changed by ".sep" configuration as following man-pages.pick.
man-pages.pick
Code: Select all
/usr/share/man/man1
/usr/share/man/man5
/usr/share/man/man7
/usr/share/man/man8
step 1: add man-pages.pick to ".sep" configuration.
It is done
in self running (APorteus-FVWM-v16.03.10-i486.iso) environment.
example: 32bit
Code: Select all
% su
# ls -1
APorteus-FVWM-v16.03.10-i486.iso
man-pages.pick
# dISO APorteus-FVWM-v16.03.10-i486.iso
# dXZM APorteus-FVWM-v16.03.10-i486/porteus/base/003-z.fvwm.xzm
# sep2pkg 003-z.fvwm
# cp man-pages.pick pkgs.003-z.fvwm/pkg.spm/slim.conf/usr/local/share/archspm/lib/picks/sep/.
# mklog pkgs.003-z.fvwm/pkg.spm/slim.conf
# mergepkgs pkgs.003-z.fvwm; mkXZM 003-z.fvwm; rm -fr 003-z.fvwm
# mv 003-z.fvwm.xzm APorteus-FVWM-v16.03.10-i486/porteus/base/.
# mkISO APorteus-FVWM-v16.03.10-i486; rm -fr APorteus-FVWM-v16.03.10-i486
(case 1)
man-pages-4.05-noarch-1.xzm is already gotten in /YOURWORK.
Its separation must be changed depending on the new configuration.
In the another directory /X, it is done as following.
Code: Select all
% su
# ls
# rearrenge /YOURWORK/man-pages-4.05-noarch-1.xzm
# ls -1
man-db-2.7.5-i686-1
man-db-2.7.5-i686-1.sep
man-db-2.7.5-i686-1.xzm
man-db-2.7.5-i686-1.xzm.sep
# mv man-db-2.7.5-i686-1.xzm man-db-2.7.5-i686-1.xzm.sep /YOURWORK/.
# rm -fr *
man-pages-4.05-noarch-1.xzm is not yet gotten.
Get it with GUI ArchAPM.
step 3: update man-pages of ISO
(continue from step 1,2)
Code: Select all
# ls -1
APorteus-FVWM-v16.03.10-i486.iso
# dISO APorteus-FVWM-v16.03.10-i486.iso
# rm APorteus-FVWM-v16.03.10-i486/porteus/modules/003-man-pages-4.04-noarch-1.sep.xzm
# cp /YOURWORK/man-db-2.7.5-i686-1.xzm APorteus-FVWM-v16.03.10-i486/porteus/modules/003-man-db-2.7.5-i686-1.xzm
# mkISO APorteus-FVWM-v16.03.10-i486; rm -fr APorteus-FVWM-v16.03.10-i486
Thanks.