Page 2 of 3

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 20 May 2016, 20:17
by brokenman
Sorry it's a big ask , I didn't realize it would be a couple of hours to re-write , in my ignorance i thought the script option could be pointed to the /tmp folder to search for the firefox.tar to use rather than the online URL address and then could use the rest of the script as normal.
That wouldn't take so long but I was thinking of writing something that allows users to choose a version they want instead of just the latest.

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 26 May 2016, 20:59
by Bogomips
MANPATH
  • As it stands:

    Code: Select all

    guest@porteus:~$ echo $MANPATH
    /usr/local/man:/usr/man:/usr/kerberos/man:/usr/kerberos/man:/usr/kerberos/man
  • but Desirable

    Code: Select all

    guest@porteus:~$ echo $MANPATH
    /usr/local/man:/usr/man:/usr/share/man:/usr/kerberos/man
For packages which follow these guidelines
Filesystem Hierarchy Standard
Filesystem Hierarchy Standard Group
...
/usr/share/man : Manual pages
Purpose

This section details the organization for manual pages throughout the system, including /usr/share/man. Also refer to the section on /var/cache/man.

The primary <mandir> of the system is /usr/share/man. /usr/share/man contains manual information for commands and data under the / and /usr filesystems. [31]

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 13 Jun 2016, 15:44
by bour59
with rc2 and now rc3 what repository to use for packages ?
from slackware 14.1 via usm
or from slackware current (14.2 ?)

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 13 Jun 2016, 18:07
by Bogomips
^ My technique being to use USM, which will resolve dependencies for package in question.. Then do separate folder download. Delete all downgrades from folder. Make module from folder whichever way you know how. Also delete giant module if one has been made and activated. When resulant module has all dependencies resolved, test it. If it works try replacing the 14.1 package with the slackware current package. :twisted:

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 14 Jun 2016, 09:25
by fullmoonremix
Salutations... :good:

Excellent strategy. I will try the CLI version of this approach.

"Best Regards"... :beer:

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 15 Jun 2016, 02:11
by brokenman
Just so you guys know ... v3.2+ has a built in command as root to download a slackware-current package: getpkg <package-name>

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 28 Jun 2016, 13:55
by azrielle
Would it be possible for you to include a Midori web browser option in build.Porteus? I recently acquired a couple of netbooks based on the feckless Intel N2600 cpu, the graphics being mostly unsupported in Linux, mostly through software, which greatly increases cpu usage. I have noticed that most browsers really bog down--even with 4GB of RAM. Less so with a truly lightweight distro such as Porteus or Manjaro Fluxbox, but still pretty bad with Firefox, Opera, or Chrome.
I noticed that the Midori bundled with Sparky Rescue loaded pages noticeably faster than the "big three" in any other distro.

And, one more request...an option to install Gnumeric along with Abiword?
Thank You.

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 28 Jun 2016, 15:06
by francois
@azrielle:

There is porteus package manager to get some of your missing software:

Code: Select all

usm -u all      #to update the manager
usm -g midori
usm -g gnumeric

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 15 Jul 2016, 21:30
by igreka
Hey all,

Not sure if this is the right place to post this or if this is relevant at all. But having had some headaches transitioning between Porteus versions over the years, and spending some time doing Nodejs development , I was thinking that it would be great to have a package.json -like feature that will list all added packages and modules in persistent mode and quickly allow a user to port his module environment from one machine to another.

Also change management to crucial config files should borrow from git enabling user to review and manually commit to changes with a smart mechanism to revert in case of errors and dumb mistakes.

I struggled this week alone with a broken USM and a broken graphical booting that is forcing me to reinstall and thus lose all the changes and setups I've made so far. I am really wishing I could retrieve my old dev environment with the flick of some magic wand.

:wall:

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 16 Jul 2016, 23:04
by Bogomips
igreka wrote:forcing me to reinstall and thus lose all the changes and setups I've made so far.
No need to install, run from iso like I do, with cop2ram. As for chnages, only used once to record setup in changes directory, thereafter only ro, so almost no chance of corruption as directory also set to ro. Otherwise most of setup done in rootcopy, cliexec and guiexec scripts, which could also be kept in the rootcopy directory. And brokenman for instance uses a setup module, so again no chance of corruption.
igreka wrote:I am really wishing I could retrieve my old dev environment with the flick of some magic wand :wall:
Did something akin to this in a very minor fashion today. Testing 3.2 Cinnamon Date & Time, resulted in the system clock being clobbered. Retrieved the time by loading 3.1 kde from iso for which had ro changes directory, and clock time now restored.

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 16 Jul 2016, 23:32
by Ed_P
igreka wrote:I am really wishing I could retrieve my old dev environment with the flick of some magic wand.

:wall:
It's called "creating backups". I backup my save.dat file periodically. and especially before I start making major changes. And I backup some of my /home/guest/ files in a folder outside of Porteus. One advantage of a backed up save.dat file is it can be renamed as a save.dat.xzm file and used as a module.

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 18 Jul 2016, 22:48
by igreka
thereafter only ro, so almost no chance of corruption as directory also set to ro
Does 'ro' stand for 'read only'. Can you please elaborate on your strategy?

Lesson learned regarding the importance of 'save.dat'. With my new installation. I will certainly start using it now.

Also, I know changes are supposed to be in rootcopy but in my case, Porteus has a changes folder populated instead.

Anyway, thanks for your responses. Should I conclude that the 'package.json' and 'git-like-diff' approaches will not be considered anytime soon? :good:

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 24 Jul 2016, 12:10
by Bogomips
igreka wrote:Can you please elaborate on your strategy?
http://forum.porteus.org/viewtopic.php? ... 426#p47426

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 26 Sep 2016, 12:56
by Michele13
Finally someone included a script to update our favorite browsers! It sucks to browse the web with firefox 31 when we are at 49. The browser version that we use in Porteus 3.1 is one year old (I'm talking about firefox). How about including chromium in the 32 bit release of Porteus to fill the gap of the missing chrome? (Chrome, as I would care about it, is no longer updated on 32bit machines, thanks google!)

Re: Porteus v3.2rc2 FAQ and wishlist

Posted: 26 Sep 2016, 21:42
by francois
Welcome back Michele. :)