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.
i'm installing slack64 current everywhere so, to make my life easier, i'm preparing a custom iso every time repo gets updated with some addons:
- 32bit compat libs (prepared for slack64 by Slamd64 people)
- additional packages i built for my own use, including wine, adobe reader and openoffice (the italian version, but you can easily build another from installed system in your language installing this package)
- an hack for enemy territory to have alsa output (for using at the same time teamspeak, listen to music, etc.) and two additional 32bit compat libs to use it.
builds: taken mainly from slackbuilds.org, some from slacky.eu, just a few others and some patches from me.
if you want to build something from here you can't launch individual slackbuilds (they need the environment variables in Addons.options, if you are brave you can try adding a ". /path/to/Addons.options" to the script), you have to:
- edit variables in Addons.options as you prefer
- then Addons.Slackbuild deleting lines for omitting compilation of some parts
- start building everything with Addons.SlackBuild
I've done this slackbuilds setup because this way I can recompile everything easily whenever I want.
Took the idea (and copied and pasted the code) from kde slackbuilds
alternatively you can simply grab code diffs and patches you need. here is a .tar of the build root.
P.S. if there's any problem redistributing such iso please let me know
I have a computer that I am giving to someone here to use. They've
never used a computer, much less owned one, so the only packages
that I need to build specifically for Chinese are Firefox, Thunderbird,
OpenOffice.org 3.1.0, and maybe QQ.
I've built Firefox-3.5.1 Chinese, but my last Slackpkg of OpenOffice
for Chinese seems to be 2.2.1. So I downloaded your package, made
a few small changes, and it seems to have worked just fine:
Code:
root@china:/home/mahui/build/openoffice/usr/src/openoffice-autobuilder-multilang/builder# sh openoffice-multilang.SlackBuild
[WARNING] you'll need about 1200MByte in /tmp/tgz to build this package [WARNING]
Start check... DONE. check is OK.
Start building...:
- clean necessary after old run
- extract tarball of openoffice and rpm inside, wait...
- reorder openoffice's directory tree
- link the mozilla-plugin
- add menu entry
- manage run file
- force gtk/gnome integration
- add documentation
cp: cannot stat `LICENSE_zh-cn*': No such file or directory
cp: cannot stat `README_zh-cn*': No such file or directory
- insert slack install files
- add pdfimport extension from http://extensions.services.openoffice.org
- add pagination extension from http://extensions.services.openoffice.org
- active all extensions (before close all process of openoffice and remove .openoffice.org* on root)
- build package, wait...
- your package is saved on /tmp/tgz
- make files checksum and desc
build done.
all done. bye ;)
I'm not entirely sure what to do with everything in this directory:
but given time will probably figure it out. Maybe the install took care of that:
Code:
root@china:/tmp/tgz# installpkg openoffice-zh-cn-3.1.0-i586-19sl.txz
Verifying package openoffice-zh-cn-3.1.0-i586-19sl.txz.
Installing package openoffice-zh-cn-3.1.0-i586-19sl.txz:
PACKAGE DESCRIPTION:
# OpenOffice.org (Free Office Suite)
#
# OpenOffice.org is both a multi-platform and multi-lingual
# office suite and an open-source project. Compatible with all
# other major office suites, the product is free to download,
# use, and distribute.
#
# This is a repackaging of the official binary distributed by
# openoffice-zh-cn.org.
#
Executing install script for openoffice-zh-cn-3.1.0-i586-19sl.txz.
Package openoffice-zh-cn-3.1.0-i586-19sl.txz installed.
If anyone is interested, here are the changes I've made to your
openoffice-multilang.SlackBuild to build a Simplified Chinese version:
Code:
mahui@china:~/build/openoffice/usr/src/openoffice-autobuilder-multilang/builder$ diff -u openoffice-multilang.SlackBuild openoffice-multilang.SlackBuild~
--- openoffice-multilang.SlackBuild 2009-07-18 11:19:58.000000000 +0800
+++ openoffice-multilang.SlackBuild~ 2009-07-05 17:48:16.000000000 +0800
@@ -55,17 +55,17 @@
NAME=openoffice
VERSION=3.1.0 # for unstable example VERSION=3.1.0rc1, remember set also DATE and DEV, in this case.
-#VERSION_LANG_x86_64=3.1.0rc2 # version of language package for slackware64
-#DATE=20090402 # only for automatic download with unstable versions
-#DATE_LANG_x86_64=20090427 # date of language package for slackware64
+VERSION_LANG_x86_64=3.1.0rc2 # version of language package for slackware64
+DATE=20090402 # only for automatic download with unstable versions
+DATE_LANG_x86_64=20090427 # date of language package for slackware64
SHORT_VERSION=$(echo $VERSION | cut -c -3)
CSHORT_VERSION=$(echo $VERSION | cut -c -1)
DEV="auto" # auto, disable or enable
ARCH="auto" # auto, i586 or x86_64
BUILD=19sl
EXTENSION="auto" # auto (tgz or txz), tgz, txz, tlz, tbz, tar.gz, tar.xz, tar.lzma, tar.bz2
-MIRROR="ftp://ftp.free.fr/mirrors/ftp.openoffice.org" #lock mirror
-ISOCODE="zh-cn" #lock language with isocode
+MIRROR="" #lock mirror
+ISOCODE="" #lock language with isocode
# NOT modify!!!
TMP=/tmp/tgz #final char is NOT "/"!!!
Notice that I had to use "zh-cn" for the ISOCODE, rather than "zh-CN" in your isocodes file.
I launched OpenOffice Writer and it seemed to work fine,
though I only typed a little bit then exited. If there
are any problems once the person begins using it, we
will report back. I don't anticipate any.
Your work, and those other people you mentioned, is what makes
the OSS community so much better than the proprietary choices.
I see slack.eu mentioned a lot around Slackware land, but since I can't read Italian,
I don't get the benefit. Maybe you could report to the script writer that little issue
about the Chinese isocodes. It keeps the script from downloading the image. I had already
downloaded the file because I was going to use my SlackBuild script for it. When I started
with yours, I put the source in /tmp/tgz but it still would not run until I changed the isocode.
submax says that there's something additionally wrong with iso code name for zh-cn and that will look for fixing it, and also that the two cp errors are harmless.
i'm happy just to have eased a little someone's else life
just trying to ease at the same time work to real packagers (I can say I'm a newbie in that), having done work myself to find/create/test working 64bit patches/build scripts for that software
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.