Slax author's Blog (RSS)

Tomas, how can I restore the system titlebar in Firefox?

In order to restore system titlebar in FireFox, go to System settings -> Workspace appearance -> Configure decoration -> Window specific Overrides and disable the rule for FireFox's title there. Then you can disable Microutilities extension in FireFox as this one cares of the buttons and window movement.

By the way, your question is absolutely off topic here under this blog post regarding buildscripts...

thanks for buildscript.
when we'll get modules and software center for slax 7.0?
currently i'm trying to make some packages (.sb) using buildscript.

Tomas M: Well maybe offtopic, but there isn't any forum, so how can we ask questions or report bugs? I don't like posting off topic, but there's no other option for us, than to be offtopic. Bugzilla would be great for bugs and some web forum for other discussion (including offtopic).

sh perl.SlaxBuild
perl.SlaxBuild: line 47: Extraction: command not found
--2012-12-13 11:11:27-- http://slackware.osuosl.org/slackware64-14.0/slackware64/d/perl-5.16.1-i486-1.txz
Resolving slackware.osuosl.org (slackware.osuosl.org)... 140.211.166.134
Connecting to slackware.osuosl.org (slackware.osuosl.org)|140.211.166.134|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-12-13 11:11:27 ERROR 404: Not Found.

i'm use this script, may be it will be useful

#!/bin/sh

if [ $# -ne 1 ]; then
echo "build package from source"
echo "usage: `basename $0` filename.{tar.gz|tar.bz2|tar.xz}"
exit 1
fi

CWD=$PWD
TMP=/tmp/BS-`uuidgen | head -c 8`
PKG=`realpath $1 || exit 1`
PREFIX=/usr

case "$( uname -m )" in
x86_64) LIBDIR=$PREFIX/lib64 ;;
i?86) LIBDIR=$PREFIX/lib ;; # $PREFIX/lib32
*) LIBDIR=$PREFIX/lib ;;
esac

mkdir $TMP
cd $TMP

tar -xvf "$PKG" || exit 1
PKGNAME=`ls $TMP`
cd $PKGNAME

[ -f CMakeLists.txt ] && cmake . -DCMAKE_INSTALL_PREFIX:PATH=$PREFIX -DLIB_SUFFIX:PATH=$LIBDIR

[ -f configure ] && ./configure --prefix=$PREFIX --libdir=$LIBDIR

NUMJOBS=${NUMJOBS:--j`cat /proc/cpuinfo | grep processor | wc -l`}
make $NUMJOBS || exit 1 # unfortunatly make don't return fail but may be

mkdir $TMP/root
make install DESTDIR=$TMP/root # make install-strip DESTDIR=$TMP/root

cd $TMP/root

# strip binaries:
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null

cd $TMP/root
tar cf - . | gzip > /tmp/$PKGNAME.tgz

echo ----------------------------------------------------------
echo Package /tmp/$PKGNAME.tgz built

rm -rf $TMP

Oh I forgot that 64bit slackware packages have different filename (they include different arch) ... SO for now the current build scripts will work only on 32bit slax. I will fix that when I return home from my trip (on train at the moment).

When will be Software Center and modules ready to use?

All this work seems be very usefull. I hope that this "slax" version of linux portable distro, will became the best portable distro. I enjoy very much and i hope the modules cames as soon as you will.
Sorry for my bugs english, but I'm an italian user of linux.

Alberto

@Tomas M, it looks like that it doesn't recognize folder names with spaces:

bash-4.2# pwd
/root/Área de trabalho
bash-4.2# slax buildscript download template
Download in progress...
stat: cannot stat ‘/root/Área/template.SlaxBuild’: No such file or directory
/sbin/slax: line 192: [: : integer expression expected

Error: Download error. Check your network connection.

If I go back to /root the command works fine.

@peter_t 2012-12-12 21:42

Don't give a script here because this page has bad behavior with "carriage return" so your script won't work.
It is better if you give to everyone a link where people can get your stuff...

Thanks.

BTW, I know how to deal with scripts...


@tdmsilvino

As you described it, I think your issue is an UTF-8 issue.
(directory naming)

@@Tomas M,
I want to compile ATI driver by myself . I download linux-kernel-3.6.9-i486-1.txz from this links http://ftp.linux.cz/pub/linux/slax/Slax-7.x-development/packages/32bit/linux-kernel-3.6.9-i486-1.txz
mkdir /root/kernel
installpkg -root /root/kernel/ /root/linux-kernel-3.6.9-i486-1.txz
mksquashfs /root/kernel/ /root/linux-kernel-3.6.9-i486-1.sb -comp xz -b 512K
put linux-kernel-3.6.9-i486-1.sb in /slax/modules
reboot.
But there is no source :(
If possible , can you tell me the correct method ? Thanks
Best regards!

<p>I'm sorry for my layout . So I post again</p>
<p>I want to compile ATI driver by myself .
</p><p align="justify">I download linux-kernel-3.6.9-i486-1.txz from this links http://ftp.linux.cz/pub/linux/slax/Slax-7.x-development/packages/32bit/linux-kernel-3.6.9-i486-1.txz
</p><p align="justify">mkdir /root/kernel
</p><p align="justify">installpkg -root /root/kernel/ /root/linux-kernel-3.6.9-i486-1.txz
</p><p align="justify">mksquashfs /root/kernel/ /root/linux-kernel-3.6.9-i486-1.sb -comp xz -b 512K
</p><p align="justify">put linux-kernel-3.6.9-i486-1.sb in /slax/modules reboot.
</p><p align="justify">But there is no source :(
</p><p align="justify">If possible , can you tell me the correct method ?
</p><p align="justify">Thanks
</p><p align="justify">Best regards!</p>

uh , I'm so sorry fo post twice and bader layout . If possible , I will delete it by myself

abiword and libreoffice exist in slackbuilds. How come it is not possible to get them into bundles with Buildscripts.

I have build kdegames including the game kigo. Though I can start kigo game in command line, how come this game and others like kmahjjong will not appear in the kde menu.

thanks. ;)

In addition it would be nice to have multilib alien/multilib/ from slackware for the compatibility of 32 bit packages with 64bit os.

the script download the both 32-bit and 64-bit version of a package source (txz), if anybody has a 32-bit distro, he/she don't need 64-bit version, but the script download that too. i think it's kinda problem for limited internet data plan users, he/she need to download both architecture although he/she don't need both!
isn't there any way to check architecture before downloading and download only the required package source (either 32-bit or 64-bit) for the system? is there any plan to implement this feature when modules and software center available?

@tdmsilvino:
thank you for bug report. It's due to a bug in /sbin/slax ... at line 482, there is a call to process $(pwd) while it should be enclosed in quotes, like "$(pwd)"

abhi_69: I am aware of that. Basically you shouldn't need this at all, all the slackware packages will be built into Slax modules very soon (hopefully yet this week), so you'll then just use "slax download perl" or even "slax activate perl" instead of downloading the buildscript and using it to get your module. The efficiency of build scripts is NOT IMPORTANT at all since the binaries will be built ON THE SLAX SERVER.

Actually, do we have to strictly stick to the template buildscripts?

Given that alot of packages already exist (packages.slackware.com, alien, etc, linuxpackages), can users write a simple script to download the package and do a txz2sb from the script itself instead of building from scratch?

You are free to do whatever you like :-) But the buildscripts for Slax are designed to be easily parsed by automated software and to compile the sb on server side and allow users to find some relevant infos in Software Center (when it is ready). So if you make modules just for yourself, feel free to do it. But when you want to share your buildscripts, you have to follow Slax template closely.

I was actually thinking in terms of sharing modules. Some software already exists as packages - like at alien slackbuild. Can our scripts that we upload to the slax server be simple enough to just download existing packages from places and convert them to .sb modules (instead of compiling)? Or someone may have already created a driver package and its available, so the script will just download that package and convert to an .sb module. These are for sharing, not for own use.

Is it possible to share what your automated software checks for when it parses the buildscripts? So that if I submit a script like the one I sent you via email it won't be rejected?

If the above isn't allowed, its alright, but may I know if you have any objections if I maintain an "unofficial download repository" for people to download modules I might want to share that have not been submitted or compiled using the slaxbuild scripts?

Thank you.

Actually a proper software for Slax should be always from a known source. For me, known source is only Slackware repository. If there is a possibility to compile the software directly on Slax then the build script should do that.

Of course if you wish to make a Skype module, while skype is not opensource and can't be compiled, it is reasonable for the build script to download the precompiled software and pack it as a module. But I don't see any single reason why to use a precompiled binaries of opensource software which actually can be compiled directly on Slax.

Tomáš, please add RSS for the new blog!

Thanks!

@lzap

+1 for RSS

RSS added. Click the small icon right next to the header "Slax author's blog"

sorry I didn't see it's done

@Tomas M
"But I don't see any single reason why to use a precompiled binaries of opensource software which actually can be compiled directly on Slax"

Really ? 8(

That sounds strange to me.

I can't imagine someone who would like to use Google Chrome or LibreOffice to download all the needed libraries and the software it self, then compile it...

Honestly I do not get it...

@Tomas M, thanks for that, hope we'll get modules and software center very soon. and also hope cool apps will be available then, like- google chrome, libreoffice, opera etc.

@Kadalka: you surely misunderstood. The end user will NOT need to compile ANYTHING. The buildscript is intended to be sent to Slax server, where it compiles, produces binaries, and those binaries are then used by users.

Thanks Tomas for your help and explanations, its much appreciated and also the rss. May I suggest having a "Like" button for comments/replies? So if people make a suggestion others can "like" it to show their support for the suggestion/comment (eg: guttaslax supporting rss request of lzap) - of course final decision is always up to you :)

@Guttaslax: Hi, long time no see :) The rss feed link (http://www.slax.org/rss.php) is at the icon with the 3 rows of dot-dashes at the top right corner of the "Slax author's Blog" title.

Just wondering if the "sign in" feature will be active soon and if it will point to the old database of users or will we need to register again? Or maybe facebook/twitter/google/OID integration? :)

>>> "why to use a precompiled binaries of opensource software which actually can be compiled directly on Slax"

1/ Because you don't have ALL the opensource software.
And some people give some binaries.

2/ Timestamping is a must for me so I could know if it's time to use Slax or not so I could download the updates for the slax distro.

3/ Sometimes, I could prefer a previous stable release...

4/ People with slow connections, will never have the ability to use it easily.
I suspected that a download manager could not handle that ?

>>> "The end user will NOT need to compile ANYTHING"

Thank you for that.

My question is about what you said because I can't believe that the average guy will be forced to compile anything.

Now EVERYONE knows that NO compilation will be done at the end user level.
You know, "build" means "compilation" in a Personal Computer in the end user mind.

(As I said, a forum is needed.)


>>> Questions
Before I will give it a try I've got a question :
As a 64bit user, I could expect that the process will give to us a native 64 Slax binary then ?
If this is the case then it could make me think.

The issue that may occur is the fact that I may be interested in a software which release is 1.2.10 when the latest is 1.2.14 that I may not like for example.

I was astonished that a porteus binary could run with Slax with NO changes at all.
(Technically speaking that is not a surprise)
I wonder if it will be the same with Slax...

Latest comment was for Tomas M

---It's difficult to send a comment here...
--- ">>>" is what you've written

@MarkDS

--- 1/ Like thing : It could be a good thing.

--- 2/

a) Register again is better...

b) Facebook integration via connect ? A very bad idea...
Even for some people Google is not a good idea.

c) OID : Hmmm... Why not...

Cheers

Hi markDS, nice to read you again.
You disappeared, I almost disappeared for a lot of reasons, one is that 36 years of computing are a lot of time for me and my eyesight.
I'm a quite static user, and once I've solved the issues I faced and helped someone on the same issues, I can't contribute more, since I'm not a specialist in this particular subject.
Now seems to be time to start again and learn something. I've posted my first question in the old forum, and I'm investigating myself about my own problem, so let's see what comes after.

-About the database of users I hope it can be migrated, also believe everyone is loving his/her profile, avatar, even the famous bulbs :-D from the old forum. However my e-mail is dead long time ago and I can't see a way to modify it.
-About Rss: I definitely don't know much about RSS, but so as it's set it only reports new threads/articles.
I wonder if it's possible to show at least the number of new comments as a fresh or updated feed, maybe connecting to the cookie system already in use in these pages. It would be appreciated expecially in the Request section, when available, to get a notification about a new post on your question.

And, by the way, thanks Tomas for your effort in the project.

Unfortunately the build script download both i486 and x86_64, which I'm on a 32bit machine!!!
it seems that it's a bug in scripts.

PS, I used to install perl on my slax machine.

@Tomas, previously when we activate any modules, if we have scripts in /etc/rc.d/init.d they get executed. This doesn't seem to be the case with "slax activate". Scripts in /etc/rc.d/init.d don't get run. Are we supposed to put them in /etc/rc.d/rc3.d together with the Slax startup scripts?