Hi all, what do you want to see on slackware desktop in future?

rkfb · 05-20-2014, 03:23 PM

For me its more a case of keeping stuff in, not adding it. I would be really disappointed if we ever lost twm and xterm.

yilez · 05-21-2014, 07:10 AM

The only thing I would like to see is more package information. I love the way pkgtool works, and don't think it should be changed, but a bit of information regarding what it depends on to build and what it depends on to run would be nice. For example, one might believe that because they don't want XFCE that they can also also get rid of GTK. However, there might be something else that relies on GTK. Would be nice if this was indicated somewhere.

In a similar idea, I might want to compile a package that needs ant to build, but not to run. Also, optional dependencies, etc.

Slackbuilds.org info files are similar to what I am thinking.

REQUIRES="jdk"

but also add

BUILD_REQUIRES="ant"
OPT_REQUIRES="gst1-plugins-base mplayer"
BUILD_OPT_REQUIRES="mplayer"

Something like that.

jtsn · 05-22-2014, 07:09 AM

Quote:

Originally Posted by yilez

The only thing I would like to see is more package information. I love the way pkgtool works, and don't think it should be changed, but a bit of information regarding what it depends on to build and what it depends on to run would be nice.

That is the task of the upstream developer to provide that information.

moisespedro · 05-22-2014, 07:11 AM

I just thought about something: dropping MD5, it is not reliable.

yilez · 05-22-2014, 07:54 AM

Quote:

Originally Posted by jtsn

That is the task of the upstream developer to provide that information.

I honestly don't know if this is a joke or not. Yes, the upstream developer provides this information, but I had the time to read through 1000+ readme files to find it all out, I would probably roll my own distro. Seeing as all this has been worked out when the distro was built, I think it would be nice to distribute the information in some form.

Didier Spaier · 05-22-2014, 08:43 AM

Quote:

Originally Posted by yilez

Seeing as all this has been worked out when the distro was built [..]

It wasn't. AFAIK Slackware is not rebuilt from scratch at each release. If you don't want to go through the hassle of finding out where you can find what's missing when you install a Slackware package, there is a simple recipe, known of all Slackers: do a full installation.

Or use Slackware derivative that already gives you that, like Salix.

Of course you can wait till Pat answer positively your request, but don't hold your breath then

.

yilez · 05-22-2014, 09:33 AM

Even though the distribution isn't rebuilt every time a release is made, it was still built in the first instance, and required compile time and run time dependencies to be considered.

The issue isn't 'I want to know what is missing', but 'what don't I need'. Agreed, this is a use-case unique to a few people, but seeing as this thread is hypothetical "what would you like to see" I don't see any harm in mentioning it.

Of course I don't expect this to be done. I'm just saying it would be nice.

ponce · 05-22-2014, 09:45 AM

yes, it would be nice, but it won't reflect the actual needs when someone will start using it: IMHO it will change so fast and in so many different ways that it would be, like it is, impossible for just one person to maintain it.

hpfeil · 05-22-2014, 09:53 AM

=-=-==--=snip=-==--=-

Code:

#!/bin/bash

## Find library dependencies for ELF executable files in /usr/bin
### [replace /usr/bin with bin to check those]

for file in /usr/bin/*
  do
    echo $file
    ldd $file
  done

=-=-=-=-snip=-=-=-=-

Darth Vader · 05-22-2014, 09:56 AM

BTW, will be nice to have LXQt as "snappy" alternative to KDE, err... XFCE.

LXQt behave well in my ARM netbook sporting 256MB RAM and a 800MHz processor.

Also, we need by default a even lightweight web browser, like NetSurf and, better, even Midori. And, no, I don't think that LYNX & LINKS can be seen as true alternatives to Firefox and Konqueror...

yilez · 05-22-2014, 10:18 AM

Quote:

Originally Posted by hpfeil

=-=-==--=snip=-==--=-

Code:

#!/bin/bash

## Find library dependencies for ELF executable files in /usr/bin
### [replace /usr/bin with bin to check those]

for file in /usr/bin/*
  do
    echo $file
    ldd $file
  done

=-=-=-=-snip=-=-=-=-

Cheers. I suspect that is as close it comes. Not quite what I'm after, but close enough.

lems · 05-22-2014, 11:17 AM

Quote:

Originally Posted by yilez

The only thing I would like to see is more package information. I love the way pkgtool works, and don't think it should be changed, but a bit of information regarding what it depends on to build and what it depends on to run would be nice. For example, one might believe that because they don't want XFCE that they can also also get rid of GTK. However, there might be something else that relies on GTK. Would be nice if this was indicated somewhere.

In a similar idea, I might want to compile a package that needs ant to build, but not to run. Also, optional dependencies, etc.

Slackbuilds.org info files are similar to what I am thinking.

REQUIRES="jdk"

but also add

BUILD_REQUIRES="ant"
OPT_REQUIRES="gst1-plugins-base mplayer"
BUILD_OPT_REQUIRES="mplayer"

Something like that.

Some third-party repositories list dependencies in PACKAGES.TXT, like slacky.eu. Example:

Code:

PACKAGE NAME:  digikam-3.5.0-i486-1sl.txz
PACKAGE LOCATION:  ./graphic/digikam/3.5.0
PACKAGE SIZE (compressed):  42875 K
PACKAGE SIZE (uncompressed):  118910 K
PACKAGE REQUIRED:  acl >= 2.2.51-i486-1,attica >= 0.4.1-i486-1,attr >= 2.4.46-i
486-1,bzip2 >= 1.0.6-i486-1,celt >= 0.11.1-i486-4sl,cups >= 1.5.4-i486-3,cxxlib
s >= 6.0.18-i486-1 | gcc-g++ >= 4.8.2-i486-1,exiv2 >= 0.23-i486-1,expat >= 2.1.
0-i486-1,faac >= 1.28-i486-10sl,ffmpeg >= 2.1.1-i486-2sl,fftw >= 3.3.3-i486-1,f
ontconfig >= 2.10.93-i486-1,freetype >= 2.5.0.1-i486-1,gamin >= 0.1.10-i486-5,g
cc >= 4.8.2-i486-1,gdk-pixbuf2 >= 2.28.2-i486-1,giflib >= 4.1.6-i486-1,glib2 >=
 2.36.4-i486-1,glibc-solibs >= 2.17-i486-7,glu >= 9.0.0-i486-1,gmp >= 5.1.3-i48
6-1,gnutls >= 3.1.16-i486-1,gst-plugins-base >= 0.10.36-i486-2,gstreamer >= 0.1
0.36-i486-2,ilmbase >= 1.0.3-i486-1,jasper >= 1.900.1-i486-3,kdelibs >= 4.10.5-
i486-2,kdepimlibs >= 4.10.5-i486-1,lame >= 3.99.5-i486-2sl,lcms >= 1.19-i486-2,
libICE >= 1.0.8-i486-1,libSM >= 1.2.2-i486-1,libX11 >= 1.6.2-i486-1,libXScrnSav
er >= 1.2.2-i486-1,libXau >= 1.0.8-i486-1,libXcursor >= 1.1.14-i486-1,libXdamag
e >= 1.1.4-i486-1,libXdmcp >= 1.1.1-i486-1,libXext >= 1.3.2-i486-1,libXfixes >=
 5.0.1-i486-1,libXft >= 2.3.1-i486-1,libXi >= 1.7.2-i486-1,libXpm >= 3.5.11-i48
6-1,libXrandr >= 1.4.2-i486-1,libXrender >= 0.9.8-i486-1,libXtst >= 1.2.2-i486-
1,libXxf86vm >= 1.1.3-i486-1,libaacplus >= 2.0.2-i486-4sl,libbluray >= 0.4.0-i4
86-1sl,libdbusmenu-qt >= 0.9.2-i486-2,libdc1394 >= 2.2.1-i486-1sl,libdrm >= 2.4
.46-i486-1,libexif >= 0.6.21-i486-1,libffi >= 3.0.13-i486-2,libgcrypt >= 1.5.3-
i486-1,libgpg-error >= 1.11-i486-1,libgphoto2 >= 2.5.2-i486-1,libgpod >= 0.8.2-
i486-1,libgsm >= 1.0.13-i486-8sl,libical >= 1.0-i486-1,libieee1284 >= 0.2.11-i4
86-3,libjpeg >= v8a-i486-2_slack14.1,libkdcraw >= 4.10.5-i486-1,libkexiv2 >= 4.
10.5-i486-1,libkipi >= 4.10.5-i486-1,libksane >= 4.10.5-i486-1,libmodplug >= 0.
8.8.4-i486-2sl,libogg >= 1.3.0-i486-1,libplist >= 1.8-i486-1,libpng >= 1.4.12-i
486-1,libraw1394 >= 2.0.7-i486-1,libtheora >= 1.1.1-i486-1,libtiff >= 3.9.7-i48
6-1,libtool >= 2.4.2-i486-2,libusb >= 1.0.9-i486-1,libusb-compat >= 0.1.4-i486-
1,libva >= 1.2.1-i486-1sl,libvorbis >= 1.3.3-i486-1,libvpx >= 1.2.0-i486-1sl,li
bxcb >= 1.9.1-i486-1,libxml2 >= 2.9.1-i486-1,libxslt >= 1.1.28-i486-1,marble >=
 4.10.5-i486-1,mesa >= 9.1.7-i486-1,net-snmp >= 5.7.2-i486-2,nettle >= 2.7.1-i4
86-1,opencore-amr >= 0.1.3-i486-8sl,opencv >= 2.4.7-i486-2sl,openexr >= 1.7.1-i
486-1,openssl >= 1.0.1e-i486-1 | openssl-solibs >= 1.0.1e-i486-1,opus >= 1.0.3-
i486-2sl,orc >= 0.4.18-i486-1sl,p11-kit >= 0.16.4-i486-1,pcre >= 8.33-i486-1,ph
onon >= 4.6.0-i486-1,qca >= 2.0.2-i486-1,qjson >= 0.8.1-i486-1 | qjson >= 0.8.1
-i486-1sl,qt >= 4.8.5-i486-2,rtmpdump >= 2.3-i486-4sl,sane >= 1.0.24-i486-1,sch
roedinger >= 1.0.11-i486-4sl,soprano >= 2.9.0-i486-1,speex >= 1.2rc1-i486-9sl,s
qlite >= 3.7.17-i486-1,strigi >= 0.7.7-i486-2,twolame >= 0.3.13-i486-4sl,udev >
= 182-i486-7,util-linux >= 2.21.2-i486-6,v4l-utils >= 0.9.5-i486-1,vo-aacenc >=
 0.1.3-i486-1sl,vo-amrwbenc >= 0.1.3-i486-1sl,x264 >= 20131119-i486-1sl,xvidcor
e >= 1.3.2-i486-5sl,xz >= 5.0.5-i486-1,zlib >= 1.2.8-i486-1,zvbi >= 0.2.35-i486
-1sl
PACKAGE CONFLICTS:
PACKAGE SUGGESTS:
PACKAGE DESCRIPTION:
digikam: digiKam (KDE4 Photo Management)
digikam:
digikam: digiKam is a simple digital photo management  application for KDE
digikam: which makes importing and  organizing  digital  photos a "snap". The
digikam: photos can be organized in albums which can be sorted chronologically
digikam: by directory layout or by custom collections. An easy to use
digikam: interface is provided that enables you to connect to  your camera
digikam: and preview download and/or delete your images.
digikam:

I guess this can then be used by slapt-get, though I don't use it.

jtsn · 05-22-2014, 12:16 PM

Quote:

Originally Posted by yilez

I honestly don't know if this is a joke or not. Yes, the upstream developer provides this information, but I had the time to read through 1000+ readme files to find it all out, I would probably roll my own distro.

If you have to read through 1000 READMEs to successfully install an application, then this application sucks. Sorry to say that.

A professional developer provides a short and clear INSTALL file, which lists all prerequisites in build order and where to find them. Large scale projects like the Mozilla products, the Chromium browser or OpenOffice bring them along.

Quote:

Seeing as all this has been worked out when the distro was built

It wasn't. That is Slackware's secret recipe for success. :-)

Didier Spaier · 05-22-2014, 12:31 PM

Code:

#/bin/bash
mkdir -p /tmp/completelyuseless
rm -f /tmp/completelyuseless/deps
touch /tmp/completelyuseless/deps
for i in /bin /usr/bin /sbin /usr/sbin /lib{,64} /usr/lib{,64} /usr/games /usr/lib{,64}/qt/bin; do
  if [ -d $i ]; then 
    find $i -maxdepth 1|grep -v ld-|xargs file|grep dynamically|awk -F ":" '{print $1}'|xargs ldd >> /tmp/completelyuseless/deps
  fi
done

Making it recursive is left to the reader as an exercise.

PS Don't tell me that it's shamelessly inefficient. I know.

szboardstretcher · 05-22-2014, 12:32 PM

That is shamefully ineffecient.