SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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 ).
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 ).
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)
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.
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."
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.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.