LinuxQuestions.org - Save this "just in case"

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Save this "just in case" (https://www.linuxquestions.org/questions/slackware-14/save-this-just-in-case-351627/)

Save this "just in case"

Quote:

# Save this "just in case":
#"GNOME" "The GNOME desktop for X" on "The GNOME series contains the GNOME desktop environment and related libraries."
#

Looks like to me Gnome could be added someday. I found this in isolinux "setpkg"

Eh? What d'you mean? I have GNOME with my Slack 10.1.

I found this in Slackware-current.

D'oh, I'm just stupid ;). Did Pat offer any reasons as to why he was taking GNOME out of Slack? I didn't hear about this, oops (although, I use Xfce now :D).

Quote:

Originally posted by Nylex
D'oh, I'm just stupid ;). Did Pat offer any reasons as to why he was taking GNOME out of Slack? I didn't hear about this, oops (although, I use Xfce now :D).

The official line is that Gnome doesn't follow standards. Specifically, it doesn't support autoconf, or at least, it ignores the "--prefix=" option and installs to its own path no matter what you tell it. Because of this, it's a nightmare to maintain binary packages of it.

Remember that most other packages don't have a problem in that respect. Most Slack packages are created with "--prefix=/work/usr" on the ./configure. Then when you do make install, they copy their files in /work/usr, which is presumably clean. From there, it's a simple task to go to /work/usr/bin, and strip the binaries so they're smaller. Then go to /work, and run "makepkg" to build a Slack-redistributable package. That's how I made packages for oscillation's Terminal program, and for the Japanese input/display apps. (the latter being about 43mb, but still a whole lot faster to install it than to download/compile the source apps)

Quote:

Most Slack packages are created with "--prefix=/work/usr" on the ./configure.

Not exactly. Slackware packages are created with "--prefix=/usr" and then "DESTDIR=/tmp/package-{somepackage}" is added to the 'make install' command to place the compiled software into a directory from where the application/ library can be easily packaged.

Quote:

Originally posted by killerbob
The official line is that Gnome doesn't follow standards. Specifically, it doesn't support autoconf, or at least, it ignores the "--prefix=" option and installs to its own path no matter what you tell it. Because of this, it's a nightmare to maintain binary packages of it.

Remember that most other packages don't have a problem in that respect. Most Slack packages are created with "--prefix=/work/usr" on the ./configure. Then when you do make install, they copy their files in /work/usr, which is presumably clean. From there, it's a simple task to go to /work/usr/bin, and strip the binaries so they're smaller. Then go to /work, and run "makepkg" to build a Slack-redistributable package. That's how I made packages for oscillation's Terminal program, and for the Japanese input/display apps. (the latter being about 43mb, but still a whole lot faster to install it than to download/compile the source apps)

Not anymore.

"GNOME-2.10 packages utilize the --prefix=option passed to configure, so you will use that and an environment variable (GNOME_PREFIX) to add flexibility to the installation."

http://www.linuxfromscratch.org/blfs...ome/gnome.html

Right. I built 2.8.3 from source-->binary and I honestly can't think of a Gnome package off hand that didn't honor the DESTDIR switch as well as --prefix=

Other than their being a strict order to follow for many packages, Gnome was EASY to build so I still don't know why Pat chucked it. I just chalked it up to him being a KDE fan..... :D