Porteus

Not quite 1.5 years ago, and I apologize for not explaining why it has not been implemented. I battled with it for a while before having a break and never going back to it. Not so easy to accomplish considering how PPM resolves deps and how python deps are fed to it manually. Resolving these second generation python dependencies will not be easy. If you have any ideas please put them forward.

If you point me to the source code parts that show me how PPM resolves deps and how *any* deps are fed to it manually, I might think of something.
It just has to be a sub-part of how PPM resolves deps, like, a secondary "if there is an entry in LIST about PACKAGE-NAME, also include the deps listed there"

@Rava

Now I am remaking PPM for multi languages.
It's dependency part has been finished.
It can be tested at package activation routine in original PPM.
It may be usefull for you to study the PPM dependency.


http://www.mediafire.com/download/d3xzy ... 3/test.xzm

[test.xzm]
opt/

./opt:
porteus-scripts/

./opt/porteus-scripts:
porteus-package-manager* ppm/

./opt/porteus-scripts/ppm:
inc/ utl/

./opt/porteus-scripts/ppm/inc:
libconf.inc libdenv.inc libmodule.inc libutil.inc
libconst.inc libexp.inc libppm.inc

./opt/porteus-scripts/ppm/utl:
dependencyAnalyzer@ dependentAnalyzer@ prepare_initial_report.utl*
dependencyAnalyzer.utl* prepare_initial_report@

Wow. This looks like some great work. Thanks very much. I will do some testing and look at integrating it into the main application.

neko wrote:@Rava

Now I am remaking PPM for multi languages.
It's dependency part has been finished.
It can be tested at package activation routine in original PPM.
It may be useful for you to study the PPM dependency.

http://www.mediafire.com/download/d3xzy ... 3/test.xzm

When I activate that xzm, and start PPM as "porteus-package-manager", and ask it about its version, it tells me Is that correct?

BTW, what md5sum does that module of yours have?

@Rava

1.Is that correct?
Yes, that is correct.
Because about version number the program routine and data are not changed.
You can check where to have been changed by "diff" command
(applying original porteus-package-manager and new one).

PPM displays version number through
(1) /opt/porteus-scripts/porteus-package-manager (line 1008)
function main_menu()
variable "ABOUT_DIALOG" definition for gtkdialog

Porteus Package Manager was .... Release date: "'$RELDATE'"

(2) /usr/lib/libppm (line 64)
variable "RELDATE" definition

export RELDATE="2 July 2013"

2.md5sum
b122b1de1ec707cec2d8d45b67f554be test.xzm

Thanks cat, I mean, neko...

Anyhow, I tried to search for GOCR, found nothing in Porteus, nothing in Slackware (Slackware), but when I search Slackware (Slacky) I get a gtkdialog with aka empty info...

I think that should not happen?

I also activated ppm-slackware-database-2.1-noarch-1.xzm and ppm-salix-index-2.1-noarch-1.xzm.
Is slacky data included in ppm-slackware-database-2.1-noarch-1.xzm or does it have its own database module?


Next issue:
When I want to update he slackware database, PPM tells me that the slackware-database module is currently activated, and when I click on "yes, deactivate", nothing happens, it keeps activated...

Thanks Rava. I'll take a look.

@Rava

Now you may study on the dependency of PPM with new PPM.

For example.
Download Porteus module "fotoxx" that have "REQUIRED-OTHER: Image-ExifTool"
Then, run "fotoxx".
This module needs 2 programs.
These can be got from slaky packages.

##==========================##
http://www.mediafire.com/download/d2h9g ... arch-0.xzm
md5sum:
8d3fcf0514c27bf068c50141072a6dfc porteus-scripts-13.11.15-noarch-0.xzm

version:
same as original

Multi-languages porteus-package-manager is offered.

Please refer "Multi-languages Porteus scripts".
http://forum.porteus.org/viewtopic.php?f=75&t=2867

Summary
1.New functions
1.1. reconfirm 'required libraries information' of module.
If execute PPM with -r option or with 'export RECONFIRM=yes', this "reconfirming" will be performed.

[default porteus-package-manager.desktop]
==========================================
[Desktop Entry]
Name=Porteus Package Manager
Comment=manage porteus packages
Exec=/opt/porteus-scripts/porteus-package-manager -r
Terminal=false
Icon=cdr
Type=Application
Categories=System;
Version=1.0
==========================================

1.2. merge libraries
After analyzing dependency, only dependent libraries can be merged into one library module.

[Example]
xplanet-1.3.0-i486-1sl.xzm (1.2M): get from slacky and convert
netpbm-10.49.02-i486-1.xzm (1.5M): dependent module that includes libnetpbm.so.10 and many other
(perform 'merge libraries' function)->
lib4xplanet-1.3.0-i486-1sl.xzm (69K): that includes only libnetpbm.so.10

1.3. download and convert library modules that are searched by "Porteus libraries search"

1.4. manipulate symbolic link modules

2.Bug fix trial
2.1.locale problem
Some commands output message are depend on locale.
Therefore these should be used with 'export LANG=C'.

2.2."Porteus Package Manager bug reports" Postby Rava » 19 Oct 2013, 18:37
'search Slackware (Slacky)' problem

2.3."Porteus Package Manager bug reports" by Rava » 28 Aug 2013, 07:56
'pygtk usually needs other deps resolved'

(1)download pygtk-2.24.0-i486-1.info
(2)modify /var/porteus/pygtk-2.24.0-i486-1.info of pygtk-2.24.0-i486-1.info
===========
REQUIRED-OTHER: python,pycairo,pygobject,
===========
(3)install pygtk-2.24.0-i486-1.info by PPM
(4)test run
% pygtk-demo

wow - this is nice
hopefully brokenman will merge your improvements to official PPM.

thanks!

Could we call this some bug. Its up to you to judge. I just want to mention, that whereas they appear in:
http://dl.porteus.org/x86_64/current/

The following packages could not be fetched thru PPM:
- skype
- printing
- firefox

Thanks.

@francois
these are bundles containing few packages merged together and bundles are not supported by PPM.
majority of ISO downloads goes through the web wizard so they should be picked up at the build time.

@fanthom:
This is the explanation. Great. So why should'nt we rename Index of /x86_64/current/modules/ to Index of /x86_64/current/bundles/?

Still this is not a bug but rather a development suggestion, maybe I am at the wrong place. Just tell me I will move it elsewhere.

Is is possible to put two different options to PPM:
1) fedora or rpm packages
2) for alien packages: I like the option of browsing the net for the alien packages. However, is it possible to automate the download of the alien slackbuild and have these built automatically?

Thanks.