Fatdog64-710 Alpha/2 [29 April 2016] [CLOSED]
Fatdog64-710 Alpha/2 [29 April 2016] [CLOSED]
Alpha2 uploaded. Basically bug fixes discussed in this thread. Same kernel, same browser, same everything, so if you don't have problems with alpha1 or if the problems are with the kernel/browser (which aren't addressed in this upload), then no point in downloading. Of course, if you want to test, you are always welcome and appreciated.
Alpha2 discussion starts on page 6 of this thread.
Download location: http://distro.ibiblio.org/fatdog/iso/alpha/710a2/ and similar URL for uoc.gr, aarned.edu, and nluug.nl.
___________________
A new Fatdog64 has arrived. Kirk (me) and James are happy to announce Fatdog64-710 Alpha.
James has been hard at work. The build system has been restructured, which among other things required altering about 1500 packages. The build system now supports a native 32bit library build. The wine package in the 710 repo supports running 32-bit and 64-bit. Everything has been updated/rebuilt/re-based. Highlights include gcc-4.8.3, glibc-2.19, ffmpeg-2.8.4, QT5 replaces QT4. Attached is a list with the package versions. It's a bit fatter than we like right now at about 300MB. So we'll be putting this fatdog on a diet soon. Special thanks to SFR for all his help. Could probably call this a beta, we've been using it for a while now.
EDIT: Kernel is 4.4.3, the same as the latest kernel made available for 702.
Brave testers are welcome, especially if they have fixes for problems
Find it here:
http://distro.ibiblio.org/fatdog/iso/alpha/710/
There may be some delay in responding due to travel and other personal things going on.
Alpha2 discussion starts on page 6 of this thread.
Download location: http://distro.ibiblio.org/fatdog/iso/alpha/710a2/ and similar URL for uoc.gr, aarned.edu, and nluug.nl.
___________________
A new Fatdog64 has arrived. Kirk (me) and James are happy to announce Fatdog64-710 Alpha.
James has been hard at work. The build system has been restructured, which among other things required altering about 1500 packages. The build system now supports a native 32bit library build. The wine package in the 710 repo supports running 32-bit and 64-bit. Everything has been updated/rebuilt/re-based. Highlights include gcc-4.8.3, glibc-2.19, ffmpeg-2.8.4, QT5 replaces QT4. Attached is a list with the package versions. It's a bit fatter than we like right now at about 300MB. So we'll be putting this fatdog on a diet soon. Special thanks to SFR for all his help. Could probably call this a beta, we've been using it for a while now.
EDIT: Kernel is 4.4.3, the same as the latest kernel made available for 702.
Brave testers are welcome, especially if they have fixes for problems
Find it here:
http://distro.ibiblio.org/fatdog/iso/alpha/710/
There may be some delay in responding due to travel and other personal things going on.
- Attachments
-
- package-versions.txt.gz
- (5.5 KiB) Downloaded 1069 times
Last edited by fatdog on Sun 04 Dec 2016, 08:02, edited 3 times in total.
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
Problems:
__________________
1. The package manager Gslapt doesn't have the correct source listed. Go to Edit-Preferences and sources, then add:
http://distro.ibiblio.org/fatdog/packages/710/
You probably will want to delete the existing sources for 700.
Notes:
__________________
1. With rare exceptions, we expect that (contributed) packages for 700 to continue to work with 710. Just note that 710 does not come with qt4, so packages that depend on qt4 would either need to install qt4-common, or load the qt4.sfs.
2. As per Fatdog tradition, 710 does not upgrade from 702, 701 or any other previous versions. That being said, 710 is close enough to 702 in many respects that re-using your existing savefile/savedir *might* work. If it doesn't, however, your first attempt should be to try to start with a fresh savefile.
__________________
1. The package manager Gslapt doesn't have the correct source listed. Go to Edit-Preferences and sources, then add:
http://distro.ibiblio.org/fatdog/packages/710/
You probably will want to delete the existing sources for 700.
Notes:
__________________
1. With rare exceptions, we expect that (contributed) packages for 700 to continue to work with 710. Just note that 710 does not come with qt4, so packages that depend on qt4 would either need to install qt4-common, or load the qt4.sfs.
2. As per Fatdog tradition, 710 does not upgrade from 702, 701 or any other previous versions. That being said, 710 is close enough to 702 in many respects that re-using your existing savefile/savedir *might* work. If it doesn't, however, your first attempt should be to try to start with a fresh savefile.
Last edited by fatdog on Sat 16 Apr 2016, 12:31, edited 1 time in total.
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
perl (from devx.sfs) is another one. 702 has perl 5.18, 710 has perl 5.20. I already found two contributed packages of mine that don't work: ExifTool and urxvt built with perl plugin support. Will there be a separate contributed repo for 710? Currently 710 gslap points to 700 contributed folder.fatdog wrote: 1. With rare exceptions, we expect that (contributed) packages for 700 to continue to work with 710. Just note that 710 does not come with qt4, so packages that depend on qt4 would either need to install qt4-common, or load the qt4.sfs.
/etc/xdg/rox.sourceforge.net/URI/file symlinks to /usr/local/bin/defaultbrowser
I thought jamesbond said in the 702 thread that the link should point to /usr/bin/rox.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
I'm downloading now. I may be able to answer my own question after I do some testing. Will this run both 32 and 64bit apps?
Posting from 710 now.
It recognized my dual monitor setup. I just had to swap them around.
32bit apps run. I have loaded 32bit-fd64.sfs and fd64-devx.sfs.
Seamonkey is not the latest and whinges it's not.
There is a dead network icon on the task bar.
First impressions are very good.
Now it's play time.
Good job guys.
Posting from 710 now.
It recognized my dual monitor setup. I just had to swap them around.
32bit apps run. I have loaded 32bit-fd64.sfs and fd64-devx.sfs.
Seamonkey is not the latest and whinges it's not.
There is a dead network icon on the task bar.
First impressions are very good.
Now it's play time.
Good job guys.
Nluug is up and running and about ten times faster at least for me in Norway...
http://ftp.nluug.nl/ibiblio/distributio ... /beta/710/
EDIT... Posting from the new and very fast FatDog710.
By looking at the menu, i can see two instances of GIMP in Graphic.
When installing, as I choose not to install bootloader, then installing bootloader window still hangs, as it did before.
Also the checking for valid disk... They must be closed manually.
Also Grub4Dos makes 2 entries for Fatdog when used... As it did before.
So now i reboot into the installation... brb
And that was fast and worked well. Now installed.
So its time to look around
Great work...
Since Sqlite is installed...
What about this little neat code here to make it do stuff for us that are not so into code_?
Look at some of the site made and the size of the CMS...
Files upload for instans. With that and Wlanmaker, we look at very small, but very handy stuff...
https://github.com/ilosuna/phpsqlitecms
Just a suggestion
http://ftp.nluug.nl/ibiblio/distributio ... /beta/710/
EDIT... Posting from the new and very fast FatDog710.
By looking at the menu, i can see two instances of GIMP in Graphic.
When installing, as I choose not to install bootloader, then installing bootloader window still hangs, as it did before.
Also the checking for valid disk... They must be closed manually.
Also Grub4Dos makes 2 entries for Fatdog when used... As it did before.
So now i reboot into the installation... brb
And that was fast and worked well. Now installed.
So its time to look around
Great work...
Since Sqlite is installed...
What about this little neat code here to make it do stuff for us that are not so into code_?
Look at some of the site made and the size of the CMS...
Files upload for instans. With that and Wlanmaker, we look at very small, but very handy stuff...
https://github.com/ilosuna/phpsqlitecms
Just a suggestion
Me too.smokey01 wrote: There is a dead network icon on the task bar.
The network monitor applet is initialized to wlan0. This is a problem when there is no wlan0 because the applet stops showing any signs of network activity even though eth0 is perfectly active. Perhaps rc.networks should configure the applet to monitor the first active interface. @jb/kirk What do you think? Network Wizard should probably too.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
broken perl backward compatibility
Perl (devx.sfs) backward compatibility is broken. This affects all my 702 packages that load perllib.so (the commands below assume my 702 packages are loaded in 710):
I can't find a solution for the missing libperl.so problem. I tried the usual recipes, LD_LIBRARY_PATH, ldconfig and symlinking, but it isn't enough. For instance, when gvim and urxvt are made to find libperl.so they throw other errors:
Another issue concerns 702 packages that add perl modules to the default (versioned) library path. When the 702 packages is loaded in 710 the older perl libray path isn't automatically included. For instance, my exiftool package built for 702 assuming perl 5.18.2 throws an error on 710:
I guess I will end up rebuilding exiftool for 710, but if someone has a better idea to keep backward compatibility in this case please chime in.
Here's a list of download links for the packages I mentioned above -- they're all for 702 !!
Code: Select all
# gvim
gvim: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
# /usr/local/bin/urxvt
/local/bin/urxvt: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
Code: Select all
# LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/perl5/5.20.0/x86_64-linux-thread-multi/CORE
# gvim
gvim: symbol lookup error: gvim: undefined symbol: PL_tmps_floor
# /usr/local/bin/urxvt
/usr/local/bin/urxvt: symbol lookup error: /mnt/home/os-fd64-702/fd64save/usr/local/bin/urxvt: undefined symbol: PL_unitcheckav
Code: Select all
# exiftool
Can't locate Image/ExifTool.pm in @INC (you may need to install the Image::ExifTool module) (@INC contains: /usr/bin/lib /usr/lib64/perl5/site_perl/5.20.0/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.20.0 /usr/lib64/perl5/vendor_perl/5.20.0/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.20.0 /usr/lib64/perl5/5.20.0/x86_64-linux-thread-multi /usr/lib64/perl5/5.20.0 .) at /usr/bin/exiftool line 33.
BEGIN failed--compilation aborted at /usr/bin/exiftool line 33.
Here's a list of download links for the packages I mentioned above -- they're all for 702 !!
- vim and gvim 7.4.691 text console/graphical text editor compiled with python/perl plugin support. FD64-700. You must load the FD64-700 devx SFS before running this vim/gvim.
txz https://www.dropbox.com/s/x0kfp2sbvb2d2 ... 1.txz?dl=1
sfs https://www.dropbox.com/s/jtp23m7s7byrs ... s.sfs?dl=1
md5 https://www.dropbox.com/s/ct7ptqaty1sbh ... 5.txt?dl=0 - exiftool 9.76 (package rev. 2). Exiftool needs perl, which is included in the Fatdog64 devx SFS. Fotoxx uses exiftool to show JPEG comments (menu Info>View Info). Findnrun 2.0 (Filmstrip plugin) uses exiftool to search inside image captions. Package includes ROXapp and ROX right-click menu entry for JPEG files. Install from package manager.
- Rxvt Unicode 9.19 Devx version. Install from package manager. forum>
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Thanks for all the feedbacks. Keep them coming.
@step - I didn't think that Perl modules would be extremely version specific. If many of them are like this, then we'll probably have to start a separate 710 contributed repo. I was hoping we can avoid this (don't want to start with a blank repo), but if this is unavoidable then so be it.
network tray-icon - I'll leave it at that. It's a one-time configuration anyway. The tray icon is part of lxqt-panel. I prefer not to have too much mucking that depends on a particular panel - we already depends too much on Rox.
@smokey01: 710 has alsa-lib 1.1.0. Apparently this may break older apps, unfortunately, because it is not ABI compatible with alsa-lib 1.0.x (702 hs 1.0.27 or 29). I haven'tr tried running 32-bit seamonkey yet.
EDIT: 32-bit seamonkey requires 32-bit libdbus-glib, which I didn't build (I only build 64-bit one). Fixed for next release.
@Atle: yeah, menu shows up because it's how the categories are set-up and how the default desktop file from Gimp configures it. I'll fix it up next release, using desktop-icon-overrides may be.
As for the installer, it's the same old from 702, nothing changed there. Try to run it from terminal ("fatdog-installer.sh") and copy paste the stuff you see in there, perhaps we can figure out what's wrong.
grub4dos - same notes. This is shinobar's creation, I haven't looked at it for ages. I'm not sure if shinobar is still maintaining it. I'm including it because there is nothing else, really. But I'll put a note and see if I can fix it later.
phpsqlitecms looks good. If I remember correctly the PHP in the repo is compiled with sqlite support, so that should work immediately.
@step - I didn't think that Perl modules would be extremely version specific. If many of them are like this, then we'll probably have to start a separate 710 contributed repo. I was hoping we can avoid this (don't want to start with a blank repo), but if this is unavoidable then so be it.
network tray-icon - I'll leave it at that. It's a one-time configuration anyway. The tray icon is part of lxqt-panel. I prefer not to have too much mucking that depends on a particular panel - we already depends too much on Rox.
@smokey01: 710 has alsa-lib 1.1.0. Apparently this may break older apps, unfortunately, because it is not ABI compatible with alsa-lib 1.0.x (702 hs 1.0.27 or 29). I haven'tr tried running 32-bit seamonkey yet.
EDIT: 32-bit seamonkey requires 32-bit libdbus-glib, which I didn't build (I only build 64-bit one). Fixed for next release.
@Atle: yeah, menu shows up because it's how the categories are set-up and how the default desktop file from Gimp configures it. I'll fix it up next release, using desktop-icon-overrides may be.
As for the installer, it's the same old from 702, nothing changed there. Try to run it from terminal ("fatdog-installer.sh") and copy paste the stuff you see in there, perhaps we can figure out what's wrong.
grub4dos - same notes. This is shinobar's creation, I haven't looked at it for ages. I'm not sure if shinobar is still maintaining it. I'm including it because there is nothing else, really. But I'll put a note and see if I can fix it later.
phpsqlitecms looks good. If I remember correctly the PHP in the repo is compiled with sqlite support, so that should work immediately.
Last edited by jamesbond on Sun 17 Apr 2016, 13:00, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I still don't understand if they are so version specific. I googled a lot looking for solutions to the first problem (libperl.so not found) and they all seem to solve that issue with LD_LIBRARY_PATH and friends. However, that fix isn't working for me and I don't know why, yet.jamesbond wrote:Thanks for all the feedbacks. Keep them coming.
@step - I didn't think that Perl modules would be extremely version specific. If many of them are like this, then we'll probably have to start a separate 710 contributed repo. I was hoping we can avoid this (don't want to start with a blank repo), but if this is unavoidable then so be it.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Atle wrote:When installing, as I choose not to install bootloader, then installing bootloader window still hangs, as it did before.
I can recreate it ('Checking for valid disk' window also hangs) in VBox (installing from CD to sda1) and happened to me few times on real HW, too.jamesbond wrote:As for the installer, it's the same old from 702, nothing changed there. Try to run it from terminal ("fatdog-installer.sh") and copy paste the stuff you see in there, perhaps we can figure out what's wrong.
It's been there ever since I started to use FD, but I seldom use the installer, so forgot about it.
I think it's some strange timing issue. Seems ok with this delay (actually, even 'sleep 0.01' will do):
Code: Select all
# diff -u /aufs/pup_ro/usr/sbin/fatdog-installer.sh /usr/sbin/fatdog-installer.sh
--- /aufs/pup_ro/usr/sbin/fatdog-installer.sh 2015-02-18 11:31:24.000000000 +0100
+++ /usr/sbin/fatdog-installer.sh 2016-04-17 14:32:22.716417776 +0200
@@ -476,6 +476,7 @@
kill $XPID 2> /dev/null
Xdialog --title "$APPTITLE" --no-buttons --infobox "$1" 0 0 1000000 &
XPID=$!
+ sleep 1
}
# helper - install grldr
#
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Package build system README says to put package directory under localpkg. However, when I do build-pkg.sh can't find my package. It works if I put my package folder in ./pkg (co-located with folder 'shell').
Bundled recipe for perl: error:
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
Second line (mine) is correct. First line (actual) fails downloading.
Bundled recipe for perl: error:
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
Second line (mine) is correct. First line (actual) fails downloading.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Yes, that's the correct location. I'll update the README.step wrote:Package build system README says to put package directory under localpkg. However, when I do build-pkg.sh can't find my package. It works if I put my package folder in ./pkg (co-located with folder 'shell').
My bad. However, don't change. It's easier for me to rename the file in ibiblio; since I found that the wrong spelling in in the entire CLFS recipesBundled recipe for perl: error:
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
SRC_URL=http://distro.ibiblio.org/fatdog/source ... -3.0.0.tar
Second line (mine) is correct. First line (actual) fails downloading.
@SFR - thanks, I'll try to reproduce and apply your fix.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Also change 'pkg' to 'source' in the README.jamesbond wrote: Yes, that's the correct location. I'll update the README.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Fatdog64-710 Alpha
Xorg wrote on my fd64save/var/log/Xorg.0.log:
... and nothing else: Black eagle on black background
Code: Select all
[ 23.678]
X.Org X Server 1.18.0
Release Date: 2015-11-09
[ 23.678] X Protocol Version 11, Revision 0
[ 23.678] Build Operating System: Linux 3.18.7 x86_64
[ 23.678] Current Operating System: Linux fatdog64 4.4.3 #2 SMP Tue Mar 1 23:25:01 AEDT 2016 x86_64
[ 23.678] Kernel command line: rootfstype=ramfs waitdev=5 initrd=initrd BOOT_IMAGE=vmlinuz
[ 23.679] Build Date: 24 December 2015 04:32:32PM
[ 23.679]
[ 23.679] Current version of pixman: 0.32.6
[ 23.679] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 23.679] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 23.679] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 17 18:08:37 2016
[ 23.688] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 23.688] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 23.703] (==) No Layout section. Using the first Screen section.
[ 23.704] (==) No screen section available. Using defaults.
[ 23.704] (**) |-->Screen "Default Screen Section" (0)
[ 23.704] (**) | |-->Monitor "<default monitor>"
[ 23.704] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 23.704] (==) Automatically adding devices
[ 23.704] (==) Automatically enabling devices
[ 23.704] (==) Automatically adding GPU devices
[ 23.704] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 23.707] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[ 23.707] Entry deleted from font path.
[ 23.708] (==) FontPath set to:
/usr/share/fonts/X11/misc/,
/usr/share/fonts/X11/TTF/,
/usr/share/fonts/X11/Type1/,
/usr/share/fonts/X11/100dpi/,
/usr/share/fonts/X11/75dpi/
[ 23.708] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 23.708] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 23.708] (II) Loader magic: 0x7b08d0
[ 23.708] (II) Module ABI versions:
[ 23.708] X.Org ANSI C Emulation: 0.4
[ 23.708] X.Org Video Driver: 20.0
[ 23.708] X.Org XInput driver : 22.1
[ 23.708] X.Org Server Extension : 9.0
[ 23.709] (II) xfree86: Adding drm device (/dev/dri/card0)
- Attachments
-
- Fatdog64-710.png
- (295 Bytes) Downloaded 827 times
-
- messages.gz
- hope that helps
- (14.75 KiB) Downloaded 388 times
L18L,
That looks like a kernel bug. I've read some posts from the drm-next people, seems they have some problems with 4.4. If you're really interested you can put in the 3.18.7 kernel from 702 by downloading it from here:
http://distro.ibiblio.org/fatdog/kernels/700/
Or wait for 710 beta and we'll upgrade the kernel to 4.5.x.
That looks like a kernel bug. I've read some posts from the drm-next people, seems they have some problems with 4.4. If you're really interested you can put in the 3.18.7 kernel from 702 by downloading it from here:
http://distro.ibiblio.org/fatdog/kernels/700/
Or wait for 710 beta and we'll upgrade the kernel to 4.5.x.
These are my findings as regards libperl.so compatibility between 700 and 710 >>ref. The gist of it is that you can mix 700 packages with 710 perl, with some care.
edit: A more complete guide is given in section "Perl Versions" of my Fatdog64 Packages thread. The paragraphs below still apply to some cases.
Packages that _embed_ the perl interpreter, like my vim-7.4.691-x86_64 and Rxvt packages, are indeed tied to the perl version that they were compiled against. So for those packages you need to install the corresponding Fatdog64-700 perl package (5.18.2), or load an equivalent perl sfs before you load the 710 devx sfs (if you do). For instance, the following are some ways to get vim with perl support installed correctly -- install/load a single line only, all elements in the order they are displayed:
perl-5.18.2-x86_64-1.txz vim-7.4.691-x86_64.txz BUT NO 710_devx.sfs!
perl-5.18.2-x86_64-1.sfs vim-7.4.691-x86_64.sfs BUT NO 710_devx.sfs!
perl-5.18.2-x86_64-1.txz 710_devx.sfs vim-7.4.691-x86_64.sfs
perl-5.18.2-x86_64-1.sfs 710_devx.sfs vim-7.4.691-x86_64.sfs
Eventually I will update my vim and Rxvt packages for perl 5.20.0 and this complication won't be necessary anymore. Meanwhile...
edit: A more complete guide is given in section "Perl Versions" of my Fatdog64 Packages thread. The paragraphs below still apply to some cases.
Packages that _embed_ the perl interpreter, like my vim-7.4.691-x86_64 and Rxvt packages, are indeed tied to the perl version that they were compiled against. So for those packages you need to install the corresponding Fatdog64-700 perl package (5.18.2), or load an equivalent perl sfs before you load the 710 devx sfs (if you do). For instance, the following are some ways to get vim with perl support installed correctly -- install/load a single line only, all elements in the order they are displayed:
perl-5.18.2-x86_64-1.txz vim-7.4.691-x86_64.txz BUT NO 710_devx.sfs!
perl-5.18.2-x86_64-1.sfs vim-7.4.691-x86_64.sfs BUT NO 710_devx.sfs!
perl-5.18.2-x86_64-1.txz 710_devx.sfs vim-7.4.691-x86_64.sfs
perl-5.18.2-x86_64-1.sfs 710_devx.sfs vim-7.4.691-x86_64.sfs
Eventually I will update my vim and Rxvt packages for perl 5.20.0 and this complication won't be necessary anymore. Meanwhile...
Last edited by step on Mon 25 Apr 2016, 06:55, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]