ArchLinux packages manager for Porteus

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
jamie81
White ninja
White ninja
Posts: 20
Joined: 20 May 2016, 21:37
Distribution: porteus 3.2rc
Location: U.S

Re: ArchLinux packages manager for Porteus

Post#76 by jamie81 » 21 May 2016, 17:00

neko wrote:"APorteus FVWM, XFCE, MATE, LXQT" were updated to v16.05.20.
------------------
kerner v4.5.5
Web browser vivaldi (version 1.1.453.59-1) with PPAPI flashplayer
Packages were updated depending on Archlinux rolling release.
------------------

Please refer to http://forum.porteus.org/viewtopic.php? ... 997#p36689


Thanks.
Im curious about your releases here. As far as a package manager goes, how would one go about installing packages from the AUR? What about dependencies being downloaded along with any package from the AUR? Do you have a Cinnamon version, and if not would you consider it? Thanks for your time

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: ArchLinux packages manager for Porteus

Post#77 by istinnjazz » 21 May 2016, 20:23

I have just tried your version of arch based porteus. Very promising work.
I have recently used nemesis and I had compiled a custom kernel (4.5.5) with nvidia propretary drivers. This kernel and driver works ok in your version also, just by copping the files nedded. Really cool, a kernel copy-paste. As an arch/manjaro user I really like the work being done in aporteus and nemesis. I had olso used an other similar arch based distro called "alphaos".

I have just tried your latest LXQT version, there are some minor bugs considering missing icons in task bar and some odd window graphics behaviour in network manager drop down lists.

I will try to learn how your SPM works, there are some bugs in GUI in the LXQT, it seems I cannot resize the frame that holds the findings after a package search. Fonts seem bigger than normal.

I still prefer the way console works in the pacman based nemesis even if it could lead in a dead end after a big update (?). But for now I cannot understand the internal workings inside your package manager.
I guess it has to do with the complexity of updates of the rolling release, versioning and dependencies etc.
I am new in porteus so I cannot express an objective opinion, I really like that there is interest in arch linux platform in porteus. I hope it will develop further alongside with the classic and respected slackware.

Good luck, i might give a try to an other version beside lxqt soon.

neko
DEV Team
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

Post#78 by neko » 22 May 2016, 11:27

@jamie81
Thank you for your interest.

1. "how would one go about installing packages from the AUR?"
ArchLinux SPM (Simple Package Manager) can not get a package from AUR.
If you need the package of AUR, you must use other ArchLinux method (example: "manjaro" live ISO).

The package (.tar.xz) ,that is gotten from AUR, is coverted to Porteus module (.xzm).

The coverted module is activated.

2. "What about dependencies being downloaded along with any package from the AUR?"
There are 3 methods in APorteus environment.
method 1: CUI (gathering libraries that link by ELF information)
method 2: GUI (gathering libraries that link by ELF information)
method 3: GUI (gathering packages that link by package information)

3. "would you consider it(Cinnamon)?"
I tried it. But the result was NG (Grafical did not start).
If it will be OK, I will offer.

If you have available time, you can create APorteus Cinnamon ISO by yourself on an APorteus environment.
If you will make it, please upload it (to this thread or to your own thread).
I would like to study it.


Thanks.

---------------------------------------------------------------------------------
[How to install an AUR package]
1. search
https://aur.archlinux.org
example:"hsetroo" package
search result:
https://aur.archlinux.org/packages/hsetroot/

2. get "snapshot": hsetroot.tar.gz
in the
https://aur.archlinux.org/packages/hsetroot/
page, at upper right "Package Actions",
click "Download snapshot"

3. boot "manjaro" live ISO
example: 64bit manjaro-xfce-16.06-pre2-x86_64.iso
set manjaro-xfce-16.06-pre2-x86_64.iso in the directory /live of the partition
uuid="f13fb6dd-25aa-455a-942d-60a0a40bf627"
whose device is differ from one that includes "hsetroot.tar.gz".

Boot by "gub2" with the following entry in the "grub.cfg".

Code: Select all

menuentry "manjaro-xfce-16.06-pre2-x86_64.iso" {
set uuid="f13fb6dd-25aa-455a-942d-60a0a40bf627"
set ISO="/live/manjaro-xfce-16.06-pre2-x86_64.iso"
search --no-floppy --fs-uuid --set=root $uuid
set mlabel="MJRO1606"
set archi="x86_64"
set dri="free"
loopback loop $ISO
linux (loop)/manjaro/boot/$archi/manjaro img_dev=UUID=$uuid img_loop=$ISO \
 misobasedir=manjaro misolabel=MJRO1606 nouveau.modeset=1 i915.modeset=1 \
 radeon.modeset=1 logo.nologo overlay=free quiet splash showopts
initrd (loop)/manjaro/boot/x86_64/manjaro.img
}
4. operation in "manjaro" live

Code: Select all

% ls
hsetroot.tar.gz
% tar -xzf hsetroot.tar.gz
% ls -1
hsetroot
hsetroot.tar.gz
% cd hsetroot
% makepkg
% ls -1
hsetroot-1.0.2-4-x86_64.pkg.tar.xz
hsetroot-1.0.2.tar.gz
pkg
PKGBUILD
src
5. operation in Aporteus environment.
example: APorteus-MATE-v16.05.20-x86_64.iso live

Code: Select all

% su
# ls
hsetroot-1.0.2-4-x86_64.pkg.tar.xz
# arch2mod hsetroot-1.0.2-4-x86_64.pkg.tar.xz
# ls -1
hsetroot-1.0.2-4-x86_64.pkg.tar.xz
hsetroot-1.0.2-x86_64-4.xzm
hsetroot-1.0.2-x86_64-4.xzm.sep
# activate hsetroot-1.0.2-x86_64-4.xzm
---------------------------------------------------------------------------------
[How to get dependencies of an AUR package]
operation in Aporteus environment.
example:
1)APorteus live: APorteus-MATE-v16.05.20-x86_64.iso
2)AUR package: hsetroot-1.0.2-x86_64-4.xzm
3)base libraries (that are not included in dependencies):
are libraries of 000-kernel.xzm, 001-core.xzm, 001-z.core.xzm
4)work storage: /mnt/sdb2/work

method 1: CUI (gathering libraries that link by ELF information)

First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm".

Code: Select all

% su
# ls
hsetroot-1.0.2-x86_64-4.xzm
# acuiDepend SIMPLEBASE=01 hsetroot-1.0.2-x86_64-4.xzm
# ls -1
hsetroot-1.0.2-x86_64-4.xzm
lib4hsetroot-1.0.2-x86_64-4.xzm
repo.5530
lib4hsetroot-1.0.2-x86_64-4.xzm is the module
that is constructed with the libraries that are dependencies of hsetroot-1.0.2-x86_64-4.xzm.

note: if base libraries are ones of 000-kernel.xzm, 001-core.xzm, 001-z.core.xzm, 002-xorg.xzm, 002-z.xorg.xzm
(# acuiDepend SIMPLEBASE=012 hsetroot-1.0.2-x86_64-4.xzm),
no dependency is needed.

method 2: GUI (gathering libraries that link by ELF information)

Code: Select all

% su
# ls
hsetroot-1.0.2-x86_64-4.xzm
# cp hsetroot-1.0.2-x86_64-4.xzm /mnt/sdb2/work/
# /usr/local/share/archspm/bin/archspm SIMPLEBASE=01
GUI operation
"Select repository" ---> MODULE
"Target selection list" ---> hsetroot-1.0.2-x86_64-4.xzm click
check "auto" button
push "Merge" button

result:
/mnt/sdb2/work/hsetroot/lib4hsetroot-1.0.2-x86_64-4.xzm

method 3: GUI (gathering packages that link by package information)

Code: Select all

% su
# ls
hsetroot-1.0.2-x86_64-4.xzm
# cp hsetroot-1.0.2-x86_64-4.xzm /mnt/sdb2/work/
# /usr/local/share/archspm/bin/archspm SIMPLEBASE=01
GUI operation
"Select repository" ---> MODULE
"Target selection list" ---> hsetroot-1.0.2-x86_64-4.xzm click
check "autoR" button
push "Merge" button

result:
/mnt/sda2/porteus/arch/pps/64/hsetroot/hsetroot.xzm

hsetroot.xzm is the module that is merged 3 modules:
hsetroot-1.0.2-x86_64-4.xzm
imlib2-1.4.9-x86_64-1.xzm
xorg-server-1.18.3-x86_64-1.xzm

---------------------------------------------------------------------------------
[How to build APorteus Cinnamon ISO]
pkgs.003-z.cinnamon.tgz (3 M)
http://www.mediafire.com/download/3t7lh ... nnamon.tgz
md5sum: 7a7cdc8d4012b758be45c1a8869a93b4 pkgs.003-z.cinnamon.tgz

operation in Aporteus environment.
example:
1)APorteus live: APorteus-MATE-v16.05.20-x86_64.iso
2)work storage: /mnt/sdb2/work

First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm".

Code: Select all

% ls -1
APorteus-MATE-v16.05.20-x86_64.iso
cinnamon.list
pkgs.003-z.cinnamon.tgz
% cat cinnamon.list
accountsservice
caribou
cinnamon
cinnamon-control-center
cinnamon-desktop
cinnamon-menus
cinnamon-screensaver
cinnamon-session
cinnamon-settings-daemon
cinnamon-translations
cjs
clutter-gtk
gcr
gnome-backgrounds
gnome-common
gnome-keyring
gnome-themes-standard
gobject-introspection
gstreamer
gtk-doc
gtk-engine-murrine
gtk-engines
gvfs
intltool
libgnomekbd
libkeybinder3
lxdm
muffin
nemo
network-manager-applet
networkmanager-openvpn
networkmanager-pptp
nm-connection-editor
polkit-gnome
python2-cairo
python2-dbus
python2-lxml
python2-pam
python2-pexpect
python2-pillow
python2-pyinotify
udisks2
% su
# acuiGetLd -l=cinnamon.list -M=pkgs.003-cinnamon
# ls -1
APorteus-MATE-v16.05.20-x86_64.iso
cinnamon.list
cinnamon.list.repo.15813
pkgs.003-cinnamon
pkgs.003-z.cinnamon.tgz
# mergepkgs pkgs.003-cinnamon
# mkXZM 003-cinnamon
# acuiDepend SIMPLEBASE=012 003-cinnamon.xzm
# dXZM lib4003-cinnamon.xzm
# tar -xzf pkgs.003-z.cinnamon.tgz
# mv lib4003-cinnamon pkgs.003-z.cinnamon/pkg.x86_64/
# dISO APorteus-MATE-v16.05.20-x86_64.iso
# dXZM APorteus-MATE-v16.05.20-x86_64/porteus/base/003-z.mate.xzm
# sep2pkg 003-z.mate
# mv pkgs.003-z.mate/pkg.spm pkgs.003-z.cinnamon/
# mergepkgs pkgs.003-z.cinnamon
# mkXZM 003-z.cinnamon
# mv APorteus-MATE-v16.05.20-x86_64 APorteus-CINNAMON-v16.05.20-x86_64
# rm APorteus-CINNAMON-v16.05.20-x86_64/porteus/base/003*.xzm
# rm APorteus-CINNAMON-v16.05.20-x86_64/porteus/modules/004-basicAPL3.xzm
# rm APorteus-CINNAMON-v16.05.20-x86_64/porteus/modules/004-flashp-21.0.0.242-x86_64-1.xzm
# rm APorteus-CINNAMON-v16.05.20-x86_64/porteus/modules/004-z.basicAPL3.xzm
# mv 003*.xzm APorteus-CINNAMON-v16.05.20-x86_64/porteus/base/
# mkISO APorteus-CINNAMON-v16.05.20-x86_64
# ls -1
003-cinnamon
003-z.cinnamon
APorteus-CINNAMON-v16.05.20-x86_64
APorteus-CINNAMON-v16.05.20-x86_64.iso
APorteus-CINNAMON-v16.05.20-x86_64.iso.md5
APorteus-MATE-v16.05.20-x86_64.iso
cinnamon.list
cinnamon.list.repo.15813
lib4003-cinnamon.xzm
pkgs.003-cinnamon
pkgs.003-z.cinnamon
pkgs.003-z.cinnamon.tgz
pkgs.003-z.mate
repo.22363
# rm -fr 003-cinnamon 003-z.cinnamon lib4003-cinnamon.xzm pkgs.003-z.mate
You can start debug your APorteus-CINNAMON-v16.05.20-x86_64.iso.

First boot APorteus-CINNAMON-v16.05.20-x86_64.iso with cheatcode 3.
In run level 3, login by root, and perform "update-cache" command.
Replace 009-caches.xzm by the following command
"mv /tmp/009-caches.xzm APorteus-CINNAMON-v16.05.20-x86_64/porteus/base/"
Remake ISO
"mkISO APorteus-CINNAMON-v16.05.20-x86_64"
Last edited by neko on 22 May 2016, 21:17, edited 2 times in total.

neko
DEV Team
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

Post#79 by neko » 22 May 2016, 13:30

@istinnjazz
Thank you for your interest.

APorteus is a low degree of completion.
Especially lxqt ISO is low.
The reason is the biggest cause is the low of my skills.
The next reason is because I am reducing the size a pretty unreasonable.
Not only available in the package unit, I use is taken out only use the libraries in the package.

In addition, APorteus is for verification purposes, so there is unfinished parts.
For example, it has to stand, etc. "unmount" error at the end of processing.
Since the end processing routine is to "unmount" a space of their own to run, it makes an error.

If you have available time, you can create your own APorteus ISO with Aporteus tools.
If you will make it, please upload it (to this thread or to your own thread).
I would like to study it.


Thanks.

-----------------------------------------------------------------------------------------------------------
[APorteus kernel (4.5.5)]
Aporteus kernel is built with "upakernel4.5" command.

upkernel-4.5.5-noarch-1.xzm (43 M)
http://www.mediafire.com/download/wuif9 ... arch-1.xzm
md5sum: 78f2b5e485cae867cf42e65ae8a25ef1 upkernel-4.5.5-noarch-1.xzm

This package includes "upakernel4.5" command, and, ".config" & "auf patch" for building 4.5.5 kernel.
Please refer to http://forum.porteus.org/viewtopic.php? ... 788#p34856


-----------------------------------------------------------------------------------------------------------
[How to modify APorteus-LXQT-v16.05.20-x86_64.iso with ArchLinux SPM tools.]
operation in Aporteus environment.
example:
1)APorteus live: APorteus-LXQT-v16.05.20-x86_64.iso
2)work storage: /mnt/sdb2/work

1. analyze the current APorteus-LXQT-v16.05.20-x86_64.iso

Code: Select all

% su
# ls -1
APorteus-LXQT-v16.05.20-x86_64.iso
# dISO APorteus-LXQT-v16.05.20-x86_64.iso
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/001-core.xzm; sep2pkg 001-core
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/001-z.core.xzm; sep2pkg 001-z.core
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/002-xorg.xzm; sep2pkg 002-xorg
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/002-z.xorg.xzm; sep2pkg 002-z.xorg
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-lxqt.xzm; sep2pkg 003-lxqt
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-z.lxqt.xzm; sep2pkg 003-z.lxqt
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/modules/004-basicAPL4.xzm; sep2pkg 004-basicAPL4
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/modules/004-z.basicAPL4.xzm; sep2pkg 004-z.basicAPL4
# ls -1
APorteus-LXQT-v16.05.20-x86_64
APorteus-LXQT-v16.05.20-x86_64.iso
pkgs.001-core
pkgs.001-z.core
pkgs.002-xorg
pkgs.002-z.xorg
pkgs.003-lxqt
pkgs.003-z.lxqt
pkgs.004-basicAPL4
pkgs.004-z.basicAPL4
# ls -1 pkgs.003-lxqt/*/
pkgs.003-lxqt/pkg.apl/:
gnome-screenshot-3.18.0-x86_64-1

pkgs.003-lxqt/pkg.gtk/:
gtk-engine-murrine-0.98.2-x86_64-2

pkgs.003-lxqt/pkg.gvfs/:
gvfs-1.28.2-x86_64-1
libatasmart-0.19-x86_64-3
udisks2-2.1.7-x86_64-1

pkgs.003-lxqt/pkg.lib/:
libcdio-paranoia-10.2+0.93+1-x86_64-1
libdbusmenu-qt5-0.9.3+16.04.20160218-x86_64-1
liblqr-0.4.2-x86_64-1
liblxqt-0.10.0-x86_64-6
libqtxdg-1.3.0-x86_64-3
libstroke-0.5.1-x86_64-6
libxcb-1.11.1-x86_64-1
libxss-1.2.2-x86_64-2

pkgs.003-lxqt/pkg.lx-util/:
lxappearance-0.6.2-x86_64-1
lxdm-0.5.3-x86_64-2
lxrandr-0.3.1-x86_64-1
lxtask-0.1.7-x86_64-1
lxterminal-0.2.0-x86_64-2

pkgs.003-lxqt/pkg.lxqt/:
lxqt-about-0.10.0-x86_64-4
lxqt-common-0.10.0-noarch-4
lxqt-config-0.10.0-x86_64-5
lxqt-globalkeys-0.10.0-x86_64-3
lxqt-notificationd-0.10.0-x86_64-3
lxqt-openssh-askpass-0.10.0-x86_64-3
lxqt-panel-0.10.0-x86_64-5
lxqt-policykit-0.10.0-x86_64-3
lxqt-powermanagement-0.10.0-x86_64-4
lxqt-qtplugin-0.10.0-x86_64-3
lxqt-runner-0.10.0-x86_64-4
lxqt-session-0.10.0-x86_64-3
lxqt-sudo-0.10.0-x86_64-3
menu-cache-1.0.1-x86_64-2

pkgs.003-lxqt/pkg.mpv/:
dcadec-0.2.0-x86_64-1
mpv-1:0.17.0-x86_64-3
smbclient-4.4.3-x86_64-1

pkgs.003-lxqt/pkg.net/:
gcr-3.20.0-x86_64-1
gnome-keyring-1:3.20.0-x86_64-1
network-manager-applet-1.2.2-x86_64-1
networkmanager-openvpn-1.2.2-x86_64-1
networkmanager-pptp-1.2.2-x86_64-1
nm-connection-editor-1.2.2-x86_64-1

pkgs.003-lxqt/pkg.noarch/:
adwaita-icon-theme-3.18.0-noarch-1
gnome-icon-theme-symbolic-3.12.0-noarch-4

pkgs.003-lxqt/pkg.pcmanfm/:
libfm-1.2.4-x86_64-1
libfm-extra-1.2.4-x86_64-1
lxmenu-data-0.1.5-noarch-1
pcmanfm-qt-0.10.0-x86_64-4
#
# ls -1 pkgs.003-z.lxqt/*/
pkgs.003-z.lxqt/pkg.noarch/:
add-icons-16.05.06-noarch-1
gnome-icon-theme-24x24-3.12.0-noarch-3
google-chrome-icon-16.05.04-noarch-1
iso-codes-3.41-noarch-1
lxqt-home-3.1-noarch-1
lxqt-icon-themes-3.1-noarch-1
oxygen-icons-4.14.3-noarch-1ftm

pkgs.003-z.lxqt/pkg.patch/:
startlxqt-1-noarch-1

pkgs.003-z.lxqt/pkg.spm/:
Alive-usb-16.02.07-noarch-1
amkslimjet-16.03.13-noarch-5
archspm-16.04.30-noarch-3
slim.conf
spmDebian-15.01.28-noarch-4
spmSlackware-15.01.28-noarch-3

pkgs.003-z.lxqt/pkg.x86_64/:
lib4003-lxqt
mini-qt5-base-5.6.0-x86_64-5
#
# ls -1R pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5
pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5:
usr
var

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/usr:
lib

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/usr/lib:
libQt5EglDeviceIntegration.so.5
libQt5EglDeviceIntegration.so.5.6.0
libQt5XcbQpa.so.5
libQt5XcbQpa.so.5.6.0
libts-1.0.so.0
libts-1.0.so.0.0.0
libxcb-icccm.so.4
libxcb-icccm.so.4.0.0
libxcb-image.so.0
libxcb-image.so.0.0.0
qt

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/usr/lib/qt:
plugins

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/usr/lib/qt/plugins:
platforms

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/usr/lib/qt/plugins/platforms:
libqeglfs.so
libqlinuxfb.so
libqminimal.so
libqminimalegl.so
libqoffscreen.so
libqxcb.so

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/var:
log

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/var/log:
packages

pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/var/log/packages:
mini-qt5-base-5.6.0-x86_64-5
#
# cat pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5/var/log/packages/mini-qt5-base-5.6.0-x86_64-5
PACKAGE NAME: mini-qt5-base-5.6.0-x86_64-5
COMPRESSED PACKAGE SIZE: K
UNCOMPRESSED PACKAGE SIZE: 1.5M
PACKAGE LOCATION: /libraries/lib4mini-qt5-base-5.6.0-x86_64-5.xzm
PACKAGE CATEGORY: ArchLinux
PACKAGE DESCRIPTION:
mini-qt5-base-5.6.0-x86_64-5: libqeglfs.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqlinuxfb.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqminimal.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqminimalegl.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqoffscreen.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqxcb.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: 
lib4mini-qt5-base-5.6.0-x86_64-5: == slim library for only mini-qt5-base-5.6.0-x86_64-5 ==
lib4mini-qt5-base-5.6.0-x86_64-5: libQt5EglDeviceIntegration.so.5 is from qt5-base-5.6.0-x86_64-5
lib4mini-qt5-base-5.6.0-x86_64-5: libQt5XcbQpa.so.5 is from qt5-base-5.6.0-x86_64-5
lib4mini-qt5-base-5.6.0-x86_64-5: libts-1.0.so.0 is from tslib-1.1-x86_64-1
lib4mini-qt5-base-5.6.0-x86_64-5: libxcb-image.so.0 is from xcb-util-image-0.4.0-x86_64-1
lib4mini-qt5-base-5.6.0-x86_64-5: libxcb-icccm.so.4 is from xcb-util-wm-0.4.1-x86_64-1
lib4mini-qt5-base-5.6.0-x86_64-5:
FILE LIST:
var
var/log
var/log/packages
var/log/packages/mini-qt5-base-5.6.0-x86_64-5
usr
usr/lib
usr/lib/libQt5XcbQpa.so.5
usr/lib/libxcb-image.so.0.0.0
usr/lib/libts-1.0.so.0.0.0
usr/lib/libQt5XcbQpa.so.5.6.0
usr/lib/libxcb-image.so.0
usr/lib/libxcb-icccm.so.4.0.0
usr/lib/qt
usr/lib/qt/plugins
usr/lib/qt/plugins/platforms
usr/lib/qt/plugins/platforms/libqlinuxfb.so
usr/lib/qt/plugins/platforms/libqoffscreen.so
usr/lib/qt/plugins/platforms/libqminimalegl.so
usr/lib/qt/plugins/platforms/libqminimal.so
usr/lib/qt/plugins/platforms/libqeglfs.so
usr/lib/qt/plugins/platforms/libqxcb.so
usr/lib/libQt5EglDeviceIntegration.so.5
usr/lib/libts-1.0.so.0
usr/lib/libQt5EglDeviceIntegration.so.5.6.0
usr/lib/libxcb-icccm.so.4
2. create pkgs.003-z.lxqt/pkg.x86_64/lib4003-lxqt
First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm".

Code: Select all

% su
# ls -1
APorteus-LXQT-v16.05.20-x86_64
pkgs.003-z.lxqt
# acuiDepend SIMPLEBASE=012 APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-lxqt.xzm
# dXZM lib4003-lxqt.xzm; rm lib4003-lxqt.xzm
# rm -fr pkgs.003-z.lxqt/pkg.x86_64/lib4003-lxqt
# mv lib4003-lxqt pkgs.003-z.lxqt/pkg.x86_64/
3. create pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5
First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm"
and download qt5-base package.

Code: Select all

% su
# ls
pkgs.003-z.lxqt
# ls -1 /mnt/sdb2/work/qt5-base*
/mnt/sdb2/work/qt5-base-5.6.0-x86_64-5.xzm
/mnt/sdb2/work/qt5-base-5.6.0-x86_64-5.xzm.sep
# dXZM /mnt/sdb2/work/qt5-base-5.6.0-x86_64-5.xzm
# mkdir -p mini-qt5-base-5.6.0-x86_64-5/usr/lib/qt/plugins
# mv qt5-base-5.6.0-x86_64-5/usr/lib/qt/plugins/platforms mini-qt5-base-5.6.0-x86_64-5/usr/lib/qt/plugins/
# rm -fr qt5-base-5.6.0-x86_64-5
# rm -fr pkgs.003-z.lxqt/pkg.x86_64/mini-qt5-base-5.6.0-x86_64-5
# mergepkgs pkgs.003-z.lxqt; mkXZM 003-z.lxqt; rm -fr 003-z.lxqt
# mv 003-z.lxqt.xzm 002-z.lxqt.xzm
# mkXZM mini-qt5-base-5.6.0-x86_64-5
# activate 002-z.lxqt.xzm
# acuiDepend SIMPLEBASE=012 mini-qt5-base-5.6.0-x86_64-5.xzm
# dXZM lib4mini-qt5-base-5.6.0-x86_64-5.xzm
# cp -a lib4mini-qt5-base-5.6.0-x86_64-5/* mini-qt5-base-5.6.0-x86_64-5/
# rm -fr lib4mini-qt5-base-5.6.0-x86_64-5*
# mv mini-qt5-base-5.6.0-x86_64-5/var/log/packages/lib4mini-qt5-base-5.6.0-x86_64-5 mini-qt5-base-5.6.0-x86_64-5/var/log/packages/mini-qt5-base-5.6.0-x86_64-5
# geany mini-qt5-base-5.6.0-x86_64-5/var/log/packages/mini-qt5-base-5.6.0-x86_64-5
# mklog mini-qt5-base-5.6.0-x86_64-5
# mv mini-qt5-base-5.6.0-x86_64-5 pkgs.003-z.lxqt/pkg.x86_64/
Reboot order to purge activating 002-z.lxqt.xzm.

Code: Select all

% su
# rm 002-z.lxqt.xzm
# mergepkgs pkgs.003-z.lxqt
# mkXZM 003-z.lxqt
edit by "geany" command to insert the lines

Code: Select all

mini-qt5-base-5.6.0-x86_64-5: libqeglfs.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqlinuxfb.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqminimal.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqminimalegl.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqoffscreen.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: libqxcb.so is from qt5-base-5.6.0-x86_64-5
mini-qt5-base-5.6.0-x86_64-5: 
4. update
First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm".

Code: Select all

% su
# ls
# acuiUpdate update
If pkgs.003-lxqt or pkgs.003-z.lxqt is updated, please rebuild pkgs.003-z.lxqt by same as 2,3 proceses.
If 004-basicAPL4.xzm or 004-z.basicAPL4.xzm is updated,
replace new pkgs.003-lxqt ,pkgs.003-z.lxqt or 004-basicAPL4.xzm and rebuild ISO with "mkISO" command.
Reboot the new ISO in order to build 004-z.basicAPL4.xzm as follow.

Code: Select all

% su
# acuiDepend SIMPLEBASE=0123 APorteus-LXQT-v16.05.20-x86_64/porteus/modules/004-basicAPL4.xzm
-----------------------------------------------------------------------------------------------------------
[Improvement example]
[old] there are qt5 libraries in "lib4" packages gathered from qt5 packages.
-->
[new] there are qt5 libraries in qt5 packages.


operation in Aporteus environment.
example:
1)APorteus live: APorteus-LXQT-v16.05.20-x86_64.iso
2)work storage: /mnt/sdb2/work

First setting work storage and site by GUI "/usr/local/share/archspm/bin/archspm".

Code: Select all

% su
# ls
APorteus-LXQT-v16.05.20-x86_64.iso
pkg.qt.list
# cat pkg.qt.list
qt5-base
qt5-script
qt5-svg
qt5-x11extras
# acuiGetLd -l=pkg.qt.list -M=pkg.qt
#
# dISO APorteus-LXQT-v16.05.20-x86_64.iso
#
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-lxqt.xzm
# sep2pkg 003-lxqt
# mv pkg.qt pkgs.003-lxqt/
# mergepkgs pkgs.003-lxqt
# mkXZM 003-lxqt
# rm -fr 003-lxqt pkgs.003-lxqt
# mv 003-lxqt.xzm APorteus-LXQT-v16.05.20-x86_64/porteus/base/
#
# acuiDepend SIMPLEBASE=012 APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-lxqt.xzm
# dXZM lib4003-lxqt.xzm
# rm lib4003-lxqt.xzm
#
# dXZM APorteus-LXQT-v16.05.20-x86_64/porteus/base/003-z.lxqt.xzm
# sep2pkg 003-z.lxqt
# rm -fr pkgs.003-z.lxqt/pkg.x86_64/*
# mv lib4003-lxqt pkgs.003-z.lxqt/pkg.x86_64/
# mergepkgs pkgs.003-z.lxqt
# mkXZM 003-z.lxqt
# rm -fr 003-z.lxqt pkgs.003-z.lxqt
# mv 003-z.lxqt.xzm APorteus-LXQT-v16.05.20-x86_64/porteus/base/
#
# mkISO APorteus-LXQT-v16.05.20-x86_64
# rm -fr APorteus-LXQT-v16.05.20-x86_64
note:
This improvement is adapted to
APorteus-LXQT-v16.05.27-i486.iso/APorteus-LXQT-v16.05.27-x86_64.iso.

neko
DEV Team
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

Post#80 by neko » 29 May 2016, 11:01

APorteus-XFCE-v16.05.27-i486.iso
Image

"APorteus FVWM, XFCE, MATE, LXQT" were updated to v16.05.27.
"APorteus LXQT" was improved a little.
------------------
kerner v4.6.0.
Web browser vivaldi (version snapshot_1.2.490.27-1) with PPAPI flashplayer
Packages were updated depending on Archlinux rolling release.
------------------

Please refer to http://forum.porteus.org/viewtopic.php? ... 997#p36689


Thanks.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: ArchLinux packages manager for Porteus

Post#81 by istinnjazz » 30 May 2016, 01:04

@ neko,
I have not used your "arch" based system yet because I work with "nemesis" at the moment, but I will try to explore the main point behind your package manager. I am used to "pacman" console commands and I guess your method is totally different than this.

Anyway, I would suggest to simplify all those desktop environments you offer here. I think you could choose your favorite in one distribution and offer openbox as standalone mode also, the user could have the ability to choose environment in the "log-in manager" after a log out (if auto-log in) and set the default one by editing the corresponding file (e.g for lxdm).
I use manjaro and I choose what ever environment I like in the log-in screen (I have 3 modes installed: openbox standalone/xfce4 and lxqt). Sometimes I prefer the minimal openbox only, without any other environment, especially when I want to have the ability to use all the available ram (especially on some old hardware). The system consumes only 100MB of RAM on a PIII 512MB machine!
I propose that you keep only 2 versions, a x86 and a x64.. and then you could offer if you like xzm files to fill more environments in the main. But I am not sure if all those are applicable here as I am new to pouters platform and my knowledge is limited, so consider this only as an idea.


I guess this could apply as a suggestion to porteus and nemesis also.

neko
DEV Team
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

Post#82 by neko » 07 Jun 2016, 07:55

@istinnjazz
Excuse my late reply.

1. "I will try to explore the main point behind your package manager"
[Archlinux simple package manager]
This is composed of a plurality of GUI and CUI commands.
All have been created in the shell scripts.
They can be analyzed by obtaining the archspm-16.04.30-noarch-5.xzm that are provided in the following thread.
http://forum.porteus.org/viewtopic.php? ... 997#p36687

I reviewed those scripts for your inspection.
Dependency bug was found.
ArchLinux database has a dependency information in the 2 ways.
But I considered one way and missed another.
This bug was fixed by updating on 2016.06.06, 07.

2. your suggestions
Item 1) "Only one distribution will be offered and user can select other and generate it."
Item 2) "openbox will be offered."

I will accept your suggestion "Item 1".
But it needs time for me to implement.
And then ,I have to think about "locales" problem.

About "Item 2", I do not know on "openbox" well.
I will study it. (already I have downloaded live version ISO of "openbox").

Your suggestions will make my uploading work lighter.
(My network environment is not good.)


Thanks.

neko
DEV Team
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

Post#83 by neko » 30 Jun 2016, 08:19

@istinnjazz
Just now I have offered "APorteus ISO builder" ISO.
It is an answer for one of your suggestions
"Only one distribution will be offered and user can select other and generate it."

In addition this builder implements the locale creating function.
Only 2 locales (English and Japanese) were available.
Now it can be selected from the locale table.
This function lack was appeared by German need of fred08155.


@all
"APorteus ISO builder" ISO (32bit/64bit) is offered.

Feature:
1. Created "APorteus ISO" can include multiple desktops.
2. Selected language ISO can be gotten.
3. Constructed packages are updated to latest ones at the create time.
4. "APorteus ISO builder" ISO itself might be updated.

Please refer to http://forum.porteus.org/viewtopic.php? ... 689#p36689


Thanks.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: ArchLinux packages manager for Porteus

Post#84 by istinnjazz » 02 Jul 2016, 00:06

Interesting progress

User avatar
francois
Contributor
Contributor
Posts: 6434
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

Post#85 by francois » 02 Jul 2016, 16:30

@istinjazz:
From what I understand, neko's project is slackware. It tries to overcome the paucity of packages available in slackware pasture by using arch linux pasture and trying to resolve dependencies for porteus slackware. Unless I am completely wrong the adaptation is difficult and far from flawless. Though efforts of neko are outstanding. Other notable efforts has been consented by bogomips to import other Linux distributions packages to porteus. And this not to mention brokenman's usm package manager, which ports to porteus most slackware derivatives to porteus.

The solution was for porteus to move to another base as distribution, namely anjaro, that triggered nenemesis development. To resolve the relatively small array of packages provided by slackware, Ubuntu could also be pretender.

@neko:
What are your thoughts about my comments?
Prendre son temps, profiter de celui qui passe.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: ArchLinux packages manager for Porteus

Post#86 by istinnjazz » 02 Jul 2016, 22:41

francois wrote:@istinjazz:
From what I understand, neko's project is slackware.
..
That is what I have thought also. Thanks for the clarification. I think you have described it clearly.
This special "arch" package manager can under certain circumstances be useful to some Slackware users.


edit: deleted to avoid further confusion
Last edited by istinnjazz on 03 Jul 2016, 06:16, edited 1 time in total.

neko
DEV Team
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

Post#87 by neko » 03 Jul 2016, 05:12

@francois
"What are your thoughts about my comments?"

1. This original thread name was "ArchLinux packages for Porteus".
Somebody has changed it to "ArchLinux packages manager for Porteus".

I reserved first 3 entries.
I intended that
the 1st entry is for "package manager",
the 2nd entry is for "misc tools",
and the 3rd entry is for "APorteus".

"APorteus" is constructed with ArckLinux Packages based on Porteus frame.
The "package manager" is "the Simple Package Manager for ArchLinux packages"(ArchSPM).

2. ArchSPM
When ArchSPM is used on Porteus v3.1 environment,
your understand is correct,
and "the adaptation is difficult and far from flawless".

But when it is used on APorteus environment,
it is a simple package manager for Archlinux packages.
The completeness of it is much less than "Pacman".
(APorteus includes ArchSPM.)

3. APorteus
APorteus is same as Nemesis.
It is Arch based Porteus.
It is not related to "Slackware".
It is related to "Porteus".

4. next trial (?)
"DPorteus" is constructed with Debian Packages based on Porteus frame.
"SPorteus" is constructed with Slackware Packages based on Porteus frame.(= Porteus?)


Thanks.



Postscript:
I have written same meaning sentences in the past entries.
But my poor English is not understood as reflecting on my intention.
I am sorry.
Last edited by neko on 03 Jul 2016, 15:42, edited 1 time in total.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: ArchLinux packages manager for Porteus

Post#88 by istinnjazz » 03 Jul 2016, 06:47

neko wrote:
"APorteus" is constructed with ArckLinux Packages based on Porteus frame.
The "package manager" is "the Simple Package Manager for ArchLinux packages"(ArchSPM).

But when it is used on APorteus environment,
it is a simple package manager for Archlinux packages.
The completeness of it is much less than "Pacman".
(APorteus includes it.)

3. APorteus
APorteus is same as Nemesis.
It is Arch based Porteus.
It is not related to "Slackware".
It is related to "Porteus".
Last time I had tried aporteus, but only for some minutes, pacman was not there, so aporteus looked like it is a not arch but something different an experimental hybrid or something.

@ neko
Your posts grow up fast, sooner or later there will be a mesh, people will not understand easily what is going on. You have to keep at least a short description and a change log at the very beginning. You have to distinguish the packager from the distribution. This topic seems like a notebook of your work, but hard to follow.

try to write this basic description anyway you can, it will be useful to be in one place and to be the first text will be read from visitors, we will try to help you correct it if there are mistakes and then post it as a reardme text for both packages manager and the distribution. Then follow with a change log, then offer the latest downloads.

So if it is an arch based distro with the porteus frame, what is the strategy behind this? An alternative to Nemesis with arch/systemd or an experimental platform only to your package manager?

User avatar
francois
Contributor
Contributor
Posts: 6434
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

Post#89 by francois » 03 Jul 2016, 22:26

@neko:

Thanks for the clarification. So aporteus is based on arch.

I will surely make some additional testing. :)
Prendre son temps, profiter de celui qui passe.

neko
DEV Team
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

Post#90 by neko » 15 Jul 2016, 16:14

@istinnjazz
1."You have to distinguish the packager from the distribution."
I apologize that this thread has become the unclear structure.

2."An alternative to Nemesis with arch/systemd or an experimental platform only to your package manager?"
This thread is mainly an experimental platform to "Archlinux Simple Package Manager".

Thanks.

P.S.
Now I am starting applying the result of "Archlinux SPM" to other distros.


@all
"APorteus ISO builder" ISOs are updated to v16.07.15.
Improvement; Speeding up of build.
WEB browsers Pale Moon and Opera are added.

Please refer to http://forum.porteus.org/viewtopic.php? ... 997#p36689

Thanks.

Post Reply