Updating slax signal #1 dating sites in colorado
A child not reared correctly could be a nightmare once they are bigger!!
Forgive me for bringing such an issue right in the middle of rc testing of porteus, the timing might not be the best.
Maybe a talented computer-wise individual could do that.
I reiterate : Playing around with ubuntu and debian xfce 4.8, I wonder if slapt-get and gslapt (gui equivalent, and analog to synaptic for apt-get) could not do a very good job as a package manager for those with plenty of space on their hdd.
To get resolution dependencies with glapt, you need to add the following source: SOURCE= From within gslapt, you will add the source going thru: Edit Add If you do not use the gui, you have to add the source in /etc/slapt-get/slaptgetrc as in: WORKINGDIR=/var/slapt-get EXCLUDE=^aaa_elflibs,^devs,^glibc-.*,^kernel-.*,^udev,.*-[0-9] dl$,x86_64 SOURCE=ftp://ftp.slackware.com/pub/slackware/s ... Using option 2 of this first post to install slapt-get and gslapt, the program do not work.
This could be usable for people with large amounts of space ... Our current package manager offers packages across slackware, slacky, slackbuilds, fidoslax and debian (soon) ... We will have a disk installer in the next version so i guess we could say we have already have a full disk installation version of porteus.Developping an /etc/slapt-get/slapt-getrc (the slapt-get config file), with an outreaching setting of repertories and sources for porteus would be a great asset.The same would benefit to the config file of slackyd another package manager, see: viewtopic.php?* cache data concerning packages and updates from package sources * supports sources from ftp, ftps, http, https, file:/// and more (libcurl) * resumes broken downloads and will verify package integrity with MD5 checksum * show packages that are available (from cached data) and installed * search package listing using POSIX and extended regular expressions by package name, location, and description * retrieve, install, and remove packages by name or by specific version * retrieve and apply updates * upgrade from one Slackware release to another in a few simple steps * show description of packages, including mirror location, version, size, dependencies (where available), conflicts (where available), suggestions (where available), description, installation status, and the package changelog entry (where available).* exclude (hold) packages from upgrades, by name or by regular expression * transaction engine for install, remove, and upgrades, reporting concise information on what is to be done, ensuring each step happens correctly * "compare package version" algorithm to prevent downgrades * recursive dependency resolution using slack-required meta-data (see FAQ) supporting hard, soft, and conditional dependencies * package conflict resolution using slack-conflicts meta-data (see FAQ) * package suggestion support for complimentary packages (see FAQ) * Package data download robustness, only writing changes if all sources download successfully as well as only downloading those sources that have changed since the last download * i18n support via GNU gettext with 26 language translations * extremely fast and easy to script with Hyperlink: Maybe you can look at FAQs for slapt-get to get in a glimpse some more specific info on the manager: I said I am no expert in terms of package manager.