Porteus

Since I presume that 2.0 will have some changes to the underlying dependencies and libraries, as compared to 1.2 (both in x86 and x86_64) how will the issue be handed in the future for the modules in http://ponce.cc/porteus/i486/ modules ...

Since me thinks, the ones there are all made for 1.2, but when for some reasons some people will have to stay with 1.2 of Porteus and cannot change to 2.0.

Therefore me thinks, both versions should best be kept online... or do I get something wrong here?

There is not a lot of changes between Slackware-14.0 and Slackware-13.37 packages. This is why we can uses some Slackware-13.37 packages on Slackware-14.0 system. Personally, i don't like the current hierarchy of the download server. We must update at each release each old links. I would symlink current to latest release and make a folder testing but older release would be put as /vX.Y as Slackware repositories are currently doing.

Cheers!

@Hamza
Personally, i don't like the current hierarchy of the download server.

Then suggest a new one. Me thinks when downloading by hand it is a neat hierarchy, then again, doing so is usually not recommended for all users anyway (because of possible missing deps, that's why that hierarchy is hidden nowadays by default anyway when you browse it, amirite?)

We must update at each release each old links.
That sure is bothersome...

I would symlink current to latest release and make a folder testing but older release would be put as /vX.Y as Slackware repositories are currently doing.

Would have done the same.

Modules folder is hidden because it was necessary to avoid some missing dependencies post which is most of time easy to solve just by running PPM instead of browse the repo from web browser. That makes end-user life happy and this give us more time to improve Porteus

Users of 1.2 can remain using the older repo. No problem.
Users of new 2.0 can use PPM for new repo or grab modules from old repo manually. No problem.
Users of 1.2 can download modules from new repo manually. No problem.
User of 1.2 can download new package manager and use new repo. No problem.

It is not so difficult to change which repo the package manager uses. If v2.0 users want to use the old repo, just replace LIBS.TXT, PACKAGES.TXT and update your /etc/ppm/porteus.conf file. If users of 1.2 want to use new repo just download the new package manager:

32bit
64bit

As for the future, who knows. We expect people will use the package manager. This way things are easy. Updating is also easy, no symlinking, changing repo or anything difficult. I don't believe slackware symlinks either. A new version, a new repo. We will try to keep the package manager as easy to use as possible. Unfortunately the ONLY person busting my balls with bugs is Fanthom. It seems nobody else is testing the package manager. C'mon guys.

As for the structure. We will leave v1.2 modules where they are, with perhaps an update to the PPM when we decide to move them. It should be seamless for people using PPM.

brokenman wrote:Unfortunately the ONLY person busting my balls with bugs is Fanthom. It seems nobody else is testing the package manager. C'mon guys.

Hey buddy, I gave you the bug report with screenshots when using dark background and very light text, and I soon will tell you how PPM is 2.0 x86_64 does that when I change XFCe's appearance...

@brokenman
i wouldn't be such optimistic with mixing of the repos between major porteus releases.
as per my libreoffice bug report to alienbob: you will never be able to resolve all deps of some slackware-13.37 packages (libreoffice is an example) in slackware-14.0 as some libs are simply too new.

i would see it like that:
Porteus-1.x users can use 1.x repo
Porteus-2.x users can use 2.x repo

once Porteus-3.0 is released 1.x repo gets deleted.
end of life for Porteus-1.x line.

I stand corrected on two counts.

Rava, thanks for the PPM bug report. This is fixed now in rc2
Fanthom. You're right. A little optimism never hurt anyone, unless they were using old slackware versions. Don't mix drinks and don't mix repo versions. You may get away with it 99% of the time, but if your laptop explodes into pieces of wire and transistors, you were warned!

fanthom wrote:once Porteus-3.0 is released 1.x repo gets deleted.
end of life for Porteus-1.x line.

When will that be? A year from now, as it was approx between 1.0 and 2.0? xD

*.0 for each Slackware releases
x.* about every 6 months, not exactly.

Hamza wrote:*.0 for each Slackware releases

Ahhhh I had no idea. One should put that info into the wikipedia article about Porteus. Using the URL of your post, of cause, cause "citation needed". xD

Is there one in our community who acts as wikipedia editor already?

Is there one in our community who acts as wikipedia editor already?

brokenman or Ahau

Hamza wrote:

Is there one in our community who acts as wikipedia editor already?

brokenman or Ahau

Soooo.... should I write both an PM, or just wait till they read this?

Why are we both so bad, eh?

Then again I could edit the article already and sent the wiki code of that part to one of both so I have helped. xD

Then again I could edit the article already and sent the wiki code of that part to one of both so I have helped.
Yes feel free to edit and send me changes.