npp.8.1.portable.7z # download icon for our bundle - mkdir -p $APPDIR/usr/share/icons/hicolor/scalable/apps - wget -O $APPDIR/usr/share/icons/hicolor/scalable/apps/npp.svg AppDir : path. rm -rf $APPDIR || true # download npp binaries - wget -c # create a new AppDir - mkdir -p $APPDIR/npp # extract binaries - 7z -o$APPDIR/npp x. So Mike, whee can I find these portables? As you know, I am a Chrome guy, let's start there.Version : 1 script : # remove AppDir from previous builds, it's always a good idea to start fresh. Nobody's forcing ANYONE to use 's just another 'option'. The choice is, as always, down to the individual user. Or, they can always be run from their 'LAUNCH' scripts. I've simply taken it a step further, that's all, and made it truly 'portable'.Įach of my portables also offers the ability to add a MenuEntry from wherever they happen to be located. However, it tended to be limited to a single, fixed location. The portable-browser concept originally evolved in Puppy as a way of keeping the browser cache - which CAN grow to huge proportions, as you know - outside of Puppy's 'save'. It's this 'duplication' that I've sought to avoid the Windows 'PortableApp' had this concept nailed-down many years ago, yet Linux developers can't seem to get their heads around it. I've always liked the 'portable' concept - AppImages, in particular, being a favourite of mine - but the one thing that's always niggled me is the way they generate yet another set of config files whenever you move them from one OS to another. And they all use 'proven' Linux apps at their heart what I've done is to package them in such a way as to keep all the config stuff/settings (which any app will generate) self-contained, in one place, so it can be moved from one system to another. They are NOT Windows 'portables', and you do NOT need WINE to run them. My 'Puppy-portables' are Linux, through & through.
0 kommentar(er)
