(old)Puppy Linux Discussion Forum

Code: Select all

mkdir -p /usr/lib64/chromium-browser/PepperFlash &&
env PPAPI_FLASH_INSTALL_DIR=/usr/lib64/chromium-browser/PepperFlash /usr/bin/latest-pepper-flash.sh

Code: Select all

Welcome to the 'dir2pet' script.
This will convert a directory into a PET package. Example, you have a 
directory named 'abiword-0.5.6' and inside that you place whatever is
needed for the package, for example usr/local/bin/abiword (the executable)
and usr/share/applications/abiword.desktop (the XDG menu file).
Whatever the packages needs, though don't worry if there is no .desktop
file as this script will ask some simple questions and optionally create
one. The package only needs a .desktop file if a menu entry is to be
created, and also an icon is required for the menu.

The directory chromium64_45.0.2454.101+pepper_19.0.0.185_lx must separate name of the package and
version number with a dash. Ex: abiword-0.5.6

The package may optionally have post-install and post-remove scripts,
named 'pinstall.sh' and 'puninstall.sh' placed at the top directory.
(to create official PETs for the Unleashed suite, see its README file
 for more information how to create these scripts properly)

If any of the above needs to be further sorted out, you can quit this
script right now by pressing CTRL-C, otherwise just press ENTER
to use the default "xz" compression or "g" then ENTER for 
"gzip" compression.
Press ENTER key or "g" and ENTER to continue: 

Step 1
A .desktop file was found here:
chromium64_45.0.2454.101+pepper_19.0.0.185_lx/usr/share/applications/chromium.desktop
So this application will have a menu entry.
If you want to change the .desktop file in any way, open it in a text editor
right now, before proceeding and make any changes you want.
In particular, check that the icon exists, and that 'Category' entry fits
into Puppy's menu hierarchy (see file /etc/xdg/menus/hierarchy).
After satisfying yourself that the .desktop file is ok, press the ENTER key
to continue this script.
Or, type 'ignore' to build pet pkg as if there is no .desktop file.
Or, type 'new' if you would like this script to ask a series of
questions and rebuild the .desktop file from scratch: 

Dependencies
Please enter a dependency-list for the PET package that is now being
created. Packages already built-in to Puppy do not need to be
explicitly named as dependencies (except a cut-down barebones version
of Puppy may not have all of these built in, so you may have to
think of the worst-case situation).
How to enter this dependency-list is shown by an example: the package
'pupdvdtool-0.5b' has the following dependency list:
+vamps,+vobcopy,+ffmpeg,+dvdauthor,+gtkdialog3
Each package name is preceded by a '+' and delimited by a ','.
NOTE1: that 'gtkdialog3' requires the GTK libraries, but it is not
       necessary to specify sub-dependencies, as if 'gtkdialog3'
       needs to be installed it has its own dependency list.
NOTE2: You can lookup the dependency-list of each package in the
       /root/.packages/Packages-* database files
NOTE3: it is not required to specify package version numbers,
       VERSION NUMBERS NOT YET SUPPORTED BY PACKAGE MANAGER
NOTE4: If you don't know what to specify, just press ENTER key
       (the package manager will still do some basic dependency checking)

Type dependency-list: 

GUI window
Press ENTER key to bring up a GUI window that will help you to create
a database entry for the package. This will be shown in a text editor
for saving somewhere, also written to file 'pet.specs' inside the pkg.
Press ENTER: 
achromium64_45.0.2454.101+pepper_19.0.0.185_lx bInternet cEMPTY dAccess the Internet echromium64_45.0.2454.101+pepper_19.0.0.185_lx f283852 gEMPTY hyes iEMPTY

chromium64_45.0.2454.101+pepper_19.0.0.185_lx|chromium64_45.0.2454.101+pepper_19.0.0.185_lx|||Internet|283852K||chromium64_45.0.2454.101+pepper_19.0.0.185_lx.pet||Access the Internet|ubuntu|trusty||

Creating package...

File ./chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar.xz created. Now converting to .pet...

chromium64_45.0.2454.101+pepper_19.0.0.185_lx.pet has been created. Finished.

If you look in chromium64_45.0.2454.101+pepper_19.0.0.185_lx you will see the new '.specs' file.
Directory chromium64_45.0.2454.101+pepper_19.0.0.185_lx is now configured correctly as a PET package
and in future you do not need to go through this script again.
You could manually edit the files if required, and create another
.pet package just by doing this:
# tar -c -f chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar chromium64_45.0.2454.101+pepper_19.0.0.185_lx/
# xz -z -9 -e chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar
# tgz2pet chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar.xz

dir2pet exited.
sfs has been converted to pet
root# 
root# chrom
chromedriver  chromium      
root# chromium 
libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
[29609:29609:1011/151335:FATAL:sandbox_seccomp_bpf_linux.cc(203)] Check failed: policy->PreSandboxHook(). 
[29579:29603:1011/151342:ERROR:socket_libevent.cc(79)] CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol
root#
root# echo "Chromium browser starts on the desktop and allow navigation on the web"
root# Chromium browser starts on the desktop and allow navigation on the web