Branches
Comments
[»]
Synaptic
by mforce - Apr 26th 2005 17:14:29
While I like slapt-get very much ( being a former Debian user ) I would
like it even more if I had Synaptic available . Since slap-get is
implemented would it be so difficult to have Synaptic ?
Apt-get for RPM has Synaptic , why shouldn't slapt-get have it ?
Right now I'm enjoying Slack's speed but I'm just about to give it up
to go back to the almost perfect apt-get+aptitude+Synaptic+huge Debian
repository .
I realise that Slackware doesn't have all that for now but even though
it has slapt-get will it ever have it all ?
I think the day for the DIY no dependencies handling are gone so it's
about time Slackware implemented a new package managment system to fully
support dependencies.
[reply]
[top]
[»]
Re: Synaptic
by Jason Woodward - Jun 2nd 2005 09:48:13
> While I like slapt-get very much (
> being a former Debian user ) I would
> like it even more if I had Synaptic
> available . Since slap-get is
> implemented would it be so difficult to
> have Synaptic ?
Hopefully glsapt will soon fill that need.
[reply]
[top]
[»]
Error
by schizo - Feb 12th 2005 14:32:16
(root@hater.telehor.org)[~]# cd slapt-get-0.9.9g
(root@hater.telehor.org)[~/slapt-get-0.9.9g]# ls
COPYING Changelog FAQ FAQ.html INSTALL Makefile README TODO
example.slapt-getrc include po slack-desc slack-required slapt-get.8
src
(root@hater.telehor.org)[~/slapt-get-0.9.9g]# pico INSTALL
(root@hater.telehor.org)[~/slapt-get-0.9.9g]# make
gcc -W -Werror -Wall -O2 -ansi -pedantic -Iinclude
-DPROGRAM_NAME="\"slapt-get\""
-DVERSION="\"0.9.9g\""
-DRC_LOCATION="\"/etc/slapt-get/slapt-getrc\""
-DENABLE_NLS -DLOCALESDIR="\"/usr/share/locale\"" -c
-o src/common.o src/common.c
In file included from src/common.c:19:
include/main.h:25:23: curl/curl.h: No such file or directory
include/main.h:26:24: curl/types.h: No such file or directory
include/main.h:27:23: curl/easy.h: No such file or directory
make: *** [src/common.o] Error 1
[reply]
[top]
[»]
Re: Error
by Jason Woodward - Feb 12th 2005 19:39:50
> -c -o src/common.o src/common.c
> In file included from src/common.c:19:
> include/main.h:25:23: curl/curl.h: No
> such file or directory
> include/main.h:26:24: curl/types.h: No
> such file or directory
> include/main.h:27:23: curl/easy.h: No
> such file or directory
> make: *** [src/common.o] Error 1
You need libcurl installed to build from source. See the list of
Dependencies above on this project's page for a link to libcurl.
[reply]
[top]
[»]
Slapt Update 1.0 Released!
by SiegeX - Feb 6th 2005 15:40:34
For those of you who are not on the slapt-get mailing lists, I'd like to
introduce you to my 'Slapt Update' script.
This script will notify you via email about new Slackware packages as they
become availible. It has the following features:
[*] Sends an email notification that includes the list of packages that
have been updated,removed or added along with the new changelog
excerpt
[*] Ability to track either current or stable
[*] Ability to automatically download (but not install) packages when new
updates are found
[*] Ability to ignore excludes
[*] Ability to report obsolete packages
[*] Ability to send the report to STDOUT rather than an email
[*] If Changelog URL stops working, a notification email will be sent
[*] Changelog report is optional
[*] Ability to have the script check for new versions of itself
Get it at http://www.atozcomp.com/slapt_update
[reply]
[top]
[»]
Dependancies check only check "packages"
by Olive Esseret - Dec 24th 2004 04:40:46
Unlike many people it, I do not like this idea of dependencies
check. It works only if we have installed the dependencies
with a "package" and won't be able to help if the required
libraries or application has been installed in another way (by
compiling it from sources for example). Almost every other
distribution (all that I know: Debian, Redhat, Mandrake,...)
split their packages in small parts which make it virtually
impossible to systematically use the "nodeps" option which is
necessary if some system componant have been installed
manually; moreover this make the uninstallation of a package
difficult because there is always a remaining library.
I would suggest that a user who want to install everything via
packages without tweaking the system himself simply use
Debian; it has indeed an excellent packagement system for
this purpose and I see no need to try to copy it. (By the way
I have switched from Mandrake to Slackware precisely
because it was virtually impossible to tweak the system
without breaking something)
A much better approach would be to add a shell script to the
package which try to guess if the package would work on the
system; no matter on how the required componants have
been installed; and warn the user if it detect something
suspicious; like the configure in autoconf.
[reply]
[top]
[»]
Re: Dependancies check only check "packages"
by Robert de Bath - Jan 12th 2005 11:06:45
> Unlike many people
Yes. Make that most! :-)
> Debian
It is quite easy to tell the debian system you have installed something
manually that does the job of some package or collection. You just use the
package "equivs" with this you tell dpkg that any 'standard' package is
installed when it isn't really.
Likewise if you want your application to actually be installed as if it's
a real debian package you use a slackware like tgz file and "alien". (I
tend to use this method)
Leftover libraries are a problem, there are tools to help (eg: debfoster),
but so far I'm not keen on those I've seen and usually end up comparing
before and after package lists.
> A much better approach would be to add a
> shell script to the
> package which try to guess
TRY is the operative word here. Your shell script will either end up
trying and failing or you've just rewritten a minimal core of dpkg in
bash.
Also your script will not help to see if it's safe to remove a library
that you _think_ is unused.
[reply]
[top]
[»]
Great program
by syn-tax - Dec 2nd 2004 04:18:06
For the most part slapt-get seems to be a fantastic program...I have always
been a debian apt fan but have now been able to switch to slackware without
giving up too much. Hopefully more packages will become available through
this system
Thanks for the great software and keep up the good work
[reply]
[top]
[»]
Error after update.
by n - Oct 24th 2004 13:41:23
I updated to the 0.9.9c and now I get the following error:
slapt-get
slapt-get: error while loading shared libraries: libidn.so.11: cannot open
shared object file: No such file or directory
I searched thru the MANIFEST.bz2 it does not contain libidn, I googled and
couldn't find anything about slackware and libidn. I've had no problems
until now.
[reply]
[top]
[»]
Re: Error after update.
by Jason Woodward - Oct 24th 2004 16:13:01
> I updated to the 0.9.9c and now I get
> the following error:
>
> slapt-get
> slapt-get: error while loading shared
> libraries: libidn.so.11: cannot open
> shared object file: No such file or
> directory
>
> I searched thru the MANIFEST.bz2 it does
> not contain libidn, I googled and
> couldn't find anything about slackware
> and libidn. I've had no problems until
> now.
Please take this to the mailing
list.
[reply]
[top]
[»]
Re: Error after update.
by Jin Ting-Yu - Jan 25th 2005 20:25:44
> I updated to the 0.9.9c and now I get
> the following error:
>
> slapt-get
> slapt-get: error while loading shared
> libraries: libidn.so.11: cannot open
> shared object file: No such file or
> directory
>
> I searched thru the MANIFEST.bz2 it does
> not contain libidn, I googled and
> couldn't find anything about slackware
> and libidn. I've had no problems until
> now.
This happened to me yesterday when I did slapt-get --upgrade (using ver.
0.9.9b). I downloaded libidn-0.5.8-i486-1.tgz
from the current tree on my favourite mirror, and installed it with
installpkg; it worked.
I think I'll stay away from doing a global upgrade again.
[reply]
[top]
[»]
Re: Error after update.
by Jason Woodward - Jan 29th 2005 18:51:22
>
> This happened to me yesterday when I did
> slapt-get --upgrade (using ver. 0.9.9b).
> I downloaded libidn-0.5.8-i486-1.tgz
> from the current tree on my favourite
> mirror, and installed it with
> installpkg; it worked.
>
> I think I'll stay away from doing a
> global upgrade again.
>
You can expect a moving target when running -current. The problem arose
when a new curl, that was built against libidn, was uploaded into -current.
Subsequent versions of slapt-get for -current/10.1 have libidn listed as a
dependency.
take care,
jason
[reply]
[top]
[»]
There is no flame war
by LinuxSneaker - May 8th 2004 21:00:04
There seems to be a dredging up of old comments that the former maintainer
of swaret made about slapt-get. The issue has long been resolved between
the folks at freshmeat, the developers of slapt-get, and all other involved
parties.
X-bone is no longer attached to the swaret development team, and I would
hope that anyone reading this would judge either program on its
merits.
LinuxSneaker
swaret maintainer
[reply]
[top]
[»]
woo! slapt-get rules
by Matthew Robinson - May 26th 2004 10:02:46
what i would like to see is the transparent resuming (which apparently is
in cvs) and the --update command to not break the package db if it doesn't
finish.
if it downloaded the new package list to a temporary location (like
slocate's updatedb does) and then replacee it, if its fine.
thanks for a great program, and for making me lazy in package instaltion.
why dont you work on a new packaging system for slackware, with full
dependany support and based on bz2 instead of gunzip (just a thought)
[reply]
[top]
[»]
Re: woo! slapt-get rules
by Matthew Robinson - May 26th 2004 10:14:15
i just remembered something which i forgot to say in my last post:
i cant code c, beyond printf and scanf, so i cant help (or implement a new
package management format), or i would
[reply]
[top]
[»]
Re: woo! slapt-get rules
by Jason Woodward - May 26th 2004 16:10:20
> what i would like to see is the
> transparent resuming (which apparently
> is in cvs) and the --update command to
> not break the package db if it doesn't
> finish.
>
> if it downloaded the new package list to
> a temporary location (like slocate's
> updatedb does) and then replacee it, if
> its fine.
Good idea, expect it in the next release, 0.9.8e. It's available in
current cvs along with download resume (which has been available since the
0.9.8a release).
[reply]
[top]
[»]
A project deserving of merit
by Paul L Daniels - Apr 6th 2004 19:29:58
I'd just like to place a comment here - after reading the rather alarming
(but strangely humorous) debacle and smear-campaign by swaret/xbone - that
I consider slapt-get an excellent project, one which should not be
'discounted' simply because it's a (supposedly) rip-off of the Debian
apt-get solution.
This is what OpenSource is about, using other people's good work, with due
credit, to create an even better solution. There is nothing, imo, wrong
with doing what Jason has done here. It is in fact the intelligent thing
to have done, as we know that apt-get is one of the best package handling
systems around.
Jason, kudo's to you - you have created an excellent system.
Paul.
--
Paul L Daniels http://www.pldaniels.com
Linux/Unix systems Internet Development
[reply]
[top]
[»]
Long time Slackware user, first time poster.
by Vlad - Feb 26th 2004 07:35:29
I've been using Slackware for 10 years. This is the best package management
system I have seen yet, for Slackware. Sorry to see the other guys trying
to ruin the comments here. Why isn't this in the distro yet?
--
"Going to war without France is like going deer hunting without your accordion." - Jed Babbin
[reply]
[top]
[»]
Hmm interesting
by Andraž 'ruskie' Levstik - Feb 5th 2004 10:06:30
well I tried slackpkg and tried swaret and for me slapt-get is still the
best one.
I miss one feature an --exclude option so that I can upgrade all but some
pkgs. I know there's an exclude option in /etc/slapt-getrc but I want it to
be dynamic.
Else this is an excelent tool. Had no problems with it.
[reply]
[top]
[»]
resumption
by rihad - Jan 5th 2004 00:00:05
Great tool, but why isn't there transparent resuming of downloads? There
still are people with 56K modem lines out here :) I don't know if you have
to tell curl something special to resume a file, but for wget it's just a
matter of adding -c. A possible simpler solution: just implement the
--print-uris option of apt-get fame. A quick and dirty patch against
slapt-get 0.9.8: http://my.baku.to/slapt-get-0.9.8.resume.diff. With it
it's relatively painless to do resumable upgrades, once I figure out where
the local files are expected to be :) I just use something like slapt-get
--no-prompt --upgrade --print-uris | sed -n '/^ftp:/,$p' | wget -c -i -
[reply]
[top]
[»]
Re: resumption
by Jason Woodward - Jan 5th 2004 10:26:17
> Great tool, but why isn't there
> transparent resuming of downloads?
See the current cvs (0.9.8a forthcoming) for initial resume support.
> A possible simpler solution:
> just implement the --print-uris option
> of apt-get fame. A quick and dirty patch
> against slapt-get 0.9.8:
> http://my.baku.to/slapt-get-0.9.8.resume.diff.
I merged in your --print-uris patch.
[reply]
[top]
[»]
Excellent product
by Chris Horry - Dec 26th 2003 09:21:14
Finally something to rival "apt-get" on Debian or
"emerge" in Gentoo. Now Slackware fans can be lazy too!
[reply]
[top]
[»]
really nifty product
by ananke - Dec 4th 2003 08:15:18
slapt-get is actually nice, great work. It does
what it's asked to, it's fast, and it works. I'm
really pleased with it - small script for crontab
and I have all my slackware servers sync'ed up
with my internal slackware mirror. [Of course I
check the packages beforehand to make sure they
will work correctly]. Few hints for slackware
users:
1) don't be fooled by the dependencies that some
other solutions claim to offer. The truth is:
there is no real dependency information that
slackware packages contain. Trust your instincts
and ldd to solve any problems.
2) Packages to be careful when updating, which
you may want to exclude:
-perl - be sure to backup your CPAN modules, if
you installed any (perl -MCPAN -e'autobundle'
will save that information, you can reinstall the
modules after upgrading perl with perl -MCPAN
-e'install Bundle::Snapshotthatyoutook'.
-all the kernel stuff, which is included in
slapt-getrc
side note: lilo in theory should be safe to
update. patrick's install script does not
overwrite your lilo.conf
Overall, decent project. It certainly works
better than some of my home-brew scripts I've
used before.
[for those interested, I use systemimager to
manage a large pool of slackware workstations.
another great project]
[reply]
[top]
[»]
memory leak and system fail after upgrade
by zwetten - Nov 17th 2003 17:21:44
First of all, slapt-get caused me lots of Memory problems and leaks, even
my kernel hung for a moment after upgrading glibc. I will NEVER use it
anymore, rip off someone else. Next, slapt-get has no Dependancy Support
for Official slackware linux packages, and is missing a huge amount of
features which i believe will never work perfectly in slapt-get, however
swaret (http://www.swaret.org) has it all, even slackpkg works better then
slapt-get. slapt-get is a pure clone of apt-get and the creator must be a
fool creating something with no creativity. And next, the creator of this
slapt-get project is a Debian user and NOT a Slackware user, are you
fooling slackware users, or what? Stop fooling slackware users and go play
with your Debian box.
Just do a scan on port 22 at software.jaos.org and you got the result of a
working Debian woody box.
Sincerly,
Zwetten
[reply]
[top]
[»]
Re: memory leak and system fail after upgrade
by Jason Woodward - Nov 18th 2003 04:31:26
> First of all, slapt-get caused me lots
> of Memory problems and leaks, even my
> kernel hung for a moment after upgrading
> glibc.
Any valid bug reports would be appreciated at [slapt-get-user at software
dot jaos dot org]
[reply]
[top]
[»]
Re: memory leak and system fail after upgrade
by irb - Nov 23rd 2003 11:01:24
>
> % First of all, slapt-get caused me lots
> % of Memory problems and leaks, even my
> % kernel hung for a moment after upgrading glibc.
>
> Any valid bug reports would be appreciated at [slapt-get-user at
software dot jaos dot org]
Y'know, I've used both swaret and slapt-get on a couple slackware systems
I administer, and they both work quite well. Each has had its problems, and
each has its strengths. That said, the rampant immaturity of the
users of swaret leads me to question whether that project itself is
mature enough for me, as an admin, to depend upon.
With that in mind, I think it's time one of us longtime slackware users
actually thanked Jason for his work, and thanked him for bringing
some of Debian's better ideas to Slackware.
--
/i.
[reply]
[top]
[»]
Re: memory leak and system fail after upgrade
by Jason Woodward - Nov 23rd 2003 11:10:31
> With that in mind, I think it's time one
> of us longtime slackware users actually
> thanked Jason for his work, and thanked
> him for bringing some of Debian's better
> ideas to Slackware.
Thank you for that, Irb.
[reply]
[top]
[»]
Re: memory leak and system fail after upgrade
by jeff covey - Nov 25th 2003 12:35:07
> First of all, slapt-get caused me lots
> of Memory problems and leaks, even my
> kernel hung for a moment after upgrading
> glibc. I will NEVER use it anymore, rip
> off someone else.
Lest anyone should take this nonsense seriously, please be aware that it
was written by Luc Cottyn (xbone), the author of swaret. He has been a
pain in the Internet's neck for at least the past year. Last May, we
received a report that he'd been spamming various IRC channels on
freenode with advertisements for swaret. We asked him to explain this,
and he blamed it on overzealous friends. He said he'd asked them to
stop, and that was that.
Until October, anyway. Then he posted a comment on forum.swaret.org
suggesting that people start spreading a rumor that slapt-get contains a
trojan. He posted three such comments on linuxpackages.net in his
inimitable l33t l4m3r style, and one on freshmeat (and probably at other
places we don't know about). He again blamed it on his users, and I
asked him to please try to get them under control.
He managed to contain himself (at least on freshmeat) until last week,
when he posted the above junk on slapt-get's page and this on swaret's:
> I am VERY VERY happy for using this
> tool. Very happy, because i stopped
> using another management tool for
> slackware (broke my box, will not name
> it, go to hell). About swaret, the
> dependency support is really NEAT. My
> gnome packages were broken every time,
> and since i use swaret for about
> 5 minutes, i have no broken libraries
> anymore, because swaret fixed them!!
> -God Bless Swaret- Congratulations also
> to be part of the official slackware
> distribution!
We decided that we'd had enough, and we removed swaret from freshmeat.
I wrote and told him that even if he wasn't involved in all of this,
that we couldn't waste our time dealing with his childish users every
few weeks.
He flew into a self-righteous flurry of emailing activity, writing us a
dozen times a day to proclaim his innocence and demand justice, reaching
a crescendo in which he told me: "You are like Bush, you are an
American who likes war and hurt innocent people."
This went on until scoop sent him a copy of a section of freshmeat's
logs which showed that the comments had been posted from the same IP
address from which he updated swaret's listing a few minutes later.
He became mysteriously silent after that, and we never heard from him
again.
I have no doubt that swaret is good and useful software, but if you use
it, please be aware of the kind of people you're involving yourself
with.
--
vs lbh pna ernq guvf, lbh'er n trrx.
[reply]
[top]
[»]
swaret smear campaign
by Dan - Oct 11th 2003 13:47:25
> i think there is a trojan in the
> slapt-get binary,
The above posting seems to be part of an organized effort to smear
slapt-get by the swaret folks. Here's a link to their forums where they
discuss it (though I wouldn't be surprised if they removed the offending
text after a while):
http://forum.swaret.org/viewtopic.php?p=1540#1540
I've also seen similar posts on userlocal and linuxpackages forums.
[reply]
[top]
[»]
Re: swaret smear campaign
by jeff covey - Oct 11th 2003 14:14:26
> The above posting seems to be part of an
> organized effort to smear slapt-get by
> the swaret folks.
Yes, the "pieterk" account was created (presumably by "pietro" who
advocates lying about slapt-get on the swaret forum) this morning,
apparently for the sole purpose of posting this drivel. I'll delete the
comment.
Thanks,
Jeff
--
vs lbh pna ernq guvf, lbh'er n trrx.
[reply]
[top]
[»]
Poor Project...
by macgiver - Sep 27th 2003 16:15:15
LOL This is very funny.
Slackware has included now two great up-to-date projects like swaret and
slackpkg. Why the hell are you creating again another apt-get alike tool?
Anyway, swaret support dependencies and got more features then slapt-get i
advise everyone to use swaret (check on freshmeat after swaret)
[reply]
[top]
[»]
Re: Poor Project...
by Jason Woodward - Sep 27th 2003 19:22:48
> LOL This is very funny.
>
> Slackware has included now two great
> up-to-date projects like swaret and
> slackpkg. Why the hell are you creating
> again another apt-get alike tool?
> Anyway, swaret support dependencies and
> got more features then slapt-get i
> advise everyone to use swaret (check on
> freshmeat after swaret)
This is covered in the FAQ.
[reply]
[top]
[»]
slapt-get rocks!
by Dan - Sep 24th 2003 18:28:56
Finally! Someone wrote a package management utility for slackware that
does it right!
Slapt-get has turned the chore of keeping current or upgrading to a new
version absolutely hassle-free! It's small and fast. Unlike the other the
utilities out there, it doesn't take forever, and you're not left guessing
whether it actually did what it said it did.
I upgraded from slackware-9.0 to slackware-current today with absolutely
no problems. I can't wait to see whats next!
[reply]
[top]
[»]
Well Done
by OpenSorce - Dec 15th 2004 21:52:12
The only thing I ever liked about Debian now available in my favorite
distro. Sir, I salute you :-)
[reply]
[top]
|
