alien.slackbook.orgYour feedback | Alien Pastures

Your feedback – Alien Pastures Alien Pastures My thoughts on Slackware, life and everything Menu Skip to content About Alien’s ARM Archive PDO Powered Photostream Privacy Policy Your feedback Your feedback Posted on July 31, 2012 by alienbob Me Do you have any questions with regard to my packages, SlackBuild scripts, other scripts, or my documentation? Or do you have a request to make? Please use this space to write down your ideas and I will try to answer. Other readers are of course also allowed to voice their thoughts about what you write. Keep your posts on topic please. No flamewars, trolling, or other nastiness allowed. This is not meant to be a replacement for LinuxQuestions.org … If the blog refuses to accept your post, then perhaps you are affected by a bug in the SQLite plugin. Check if your post contains a string of text which is enclosed by the characters ( ). Is there a pipe symbol or a comma inside those round brackets? Try to remove those and re-post your comment. Continue to my blog articles if you want. Eric Like this: Like Loading... 1,087 thoughts on “ Your feedback ” aiden July 31, 2012 at 18:25 Thanks for creating this space, and for being such a force for the Slackware community. Reply aiden July 31, 2012 at 22:57 Okay, so the good news is that Handbrake 0.9.8 works perfectly. The bad news is it doesn’t contain any features, only bug fixes. And according to the devs, the current trunk won’t be released as the official build until next year – https://forum.handbrake.fr/viewtopic.php?f=12&t=24951 . Is there any way I could get you to build the 4883svn nightly ( https://trac.handbrake.fr/browser/trunk?rev=4883 )? Reply cesarion76 August 1, 2012 at 03:53 hi, just noticed the handbreak package in “restricted_slackbuilds” is still version 0.9.5 in 32/64 versions. Do I get all the features if I get the regular pkg from slackware.com server? best regards Reply alienbob August 1, 2012 at 11:07 O… I forgot that I had to place the packages in restricted_slackbuilds due to the lame and faac encoders… I will set that right tonight and update the repositories. Actually, it is easy for you to build your own package from a SVN trunk checkout. I will stick to the official releases but you can grab the SlackBuild and edit it so that it has these two lines: VERSION=${VERSION:-r4883} RELREV=${RELREV:-“”} Which causes the script to checkout revision 4883 from trunk and build a package for that. Eric Reply aiden August 1, 2012 at 16:23 Thanks Bob. Unfortunately it’s not going to be that simple, because sourceforge.net only has the official releases. It looks like the only way to grab a nightly for a build is to use a subversion repository call, which is failing badly for me when I try it. Reply aiden August 1, 2012 at 16:55 Hm… I reread your post, and understand my confusion now. The current .build file contains no references to SVN, so it defaulted to sourceforge. Reply aiden August 2, 2012 at 00:42 Well, after a lengthy process of finding all the dependencies necessary for a compile in unRAID, I have a working executable. I’m not 100% of the best way to make it into a package, though. I ran “make install” in the build directory and that has me going for now, but is there a simple way to make the .build file? Reply cesarion76 August 2, 2012 at 03:57 Hi Eric, slackpkg won’t blacklist last multilib update Mon Jul 30 20:12:24 UTC 2012 current/gcc-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. current/gcc-g++-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. current/gcc-gfortran-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. Fixed the 64-bit libgfortranbegin.a library which got overwritten by the 32-bit version. Thanks to hiptobecubic for reporting this. current/gcc-gnat-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. current/gcc-go-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. current/gcc-java-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. current/gcc-objc-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. I had to add: “[0-9]+fix1_alien” to /etc/slackpkg/blacklist so they don’t get replace by slackware’s native pkg best regards Reply alienbob August 2, 2012 at 08:59 Hi cesarion76 I think I may have to rename the packages so that they end on “fix1_1alien” instead of “1fix1_alien” because having to add yet another line to the blacklist file of slackpkg is not an elegant solution. Thanks for mentioning it. Cheers, Eric Reply alienbob August 2, 2012 at 09:01 aiden, I am a bit confused as to what you are trying. A “.build” file? Could you not just use the hints I gave 6 comments back and run the edited handbrake.SlackBuild with changed variable definitions? That will checkout a trunk snapshot and build that for you. Eric Reply aiden August 2, 2012 at 16:44 Bob, yes I tried that first, of course. But I got an “invalid scheme” error. So instead I went down the road of manually checking it out and compiling it locally based on Handbrake’s wiki instructions. What I would like to do is make a package out of that binary so I can post it on the unRAID forums for other users to download. I appreciate your patience, because I’m clearly a novice at these things. Reply alienbob August 2, 2012 at 21:14 I never saw an “invalid scheme” error. Perhaps if you can post a full log of your failed compilation on http://pastebon.com/ then I could have a look at it. Eric Reply gbdj August 21, 2012 at 17:50 Hi. Are there any difficulties in building recent qemu-kvm-1.1.1 for slack 13.1 or 0.14 packages just left from old SlackBuild version? Thank you Reply Colint September 10, 2012 at 07:43 Thanks Eric for the kde 4.9.1, it has helped me out a lot. Reply Krisz September 27, 2012 at 09:53 Hello Erik! Could you please create a package for virt-manager? Or create a howto how we can install it? I found some howtos on the net for slackware and virt-manager, but I was unable to make it. Thank you. Krisz Reply alienbob September 27, 2012 at 14:34 Hi Krisz I have been looking at virt-manager, especially for the VNC viewer features, and it is possible that I will create packages and/or write an article about it, when I get some free time. Eric Reply willian October 3, 2012 at 17:11 Alien, everyone would like to know how is your perfect Slackware installation, from beginning to end, partitioning, filesystem, packages, tweaks and also a screenshot of your computer, this can be an upcoming article. Reply alienbob October 3, 2012 at 18:05 Hi willian My own computers are not all that interesting to talk about. They are functional but not shiny. I add only a few packages to a full Slackware install, depending on the needs (my laptop for work has some other stuff than the desktop I share with the family). Even the background on this laptop is the standard KDE bakground… Eric Reply Duodecimo October 15, 2012 at 11:32 Hi Eric First of all I wish to thank you for the amazing packages you place and all the contribution you do for slackware. In your post about LibreOffice, you mentioned somewhere that packages under 13.37 might work for 14.0. I wonder if I should try it for lame and others, in the restricted packages, or wine, in the regular ones, and even for packages for older versions, like xawtv for 12.0 (I have multilib installed). I am using slackware 14.0. cheers! Reply alienbob October 15, 2012 at 14:41 Hi Duodecimo. The golden rule for binary packages is, if they are not available for the Slackware release you are currently using, try a package for an older release. Often that will just work (but not always). If I find a package for Slackware 13.37 which fails on Slackware 14 then I will specifically compile a new package for Slackware 14. So, yes, you can use the “older” packages for lame and wine. If you encounter any issues, like library linking errors. let me know so that I can compile a new package! With sources it is different. You will find that often, the source for an older version of software will no longer compile on a newer Linux distribution. That is typically caused by u...