[Slackbuilds-users] Enable maps in texlive-texmf-extra ?
Hi all,
When I compiling an English tex document
with \usepackage[bitstream-charter]{mathdesign} , it gives error like this:
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+546/600 --dpi 1146
md-chb8y
mktexpk: don't know how to create bitmap font for md-chb8y.
mktexpk: perhaps md-chb8y is missing from the map file.
And the same happened to futb8r. After Googling, I tried:
updmap-sys --enable Map mdbch.map
updmap-sys --enable Map fourier.map
and the problem gone. Should we add these commands to doinst.sh
of texlive-texmf-extra?
Besieds, are there any other maps we should "enable" in doinst.sh?
--
Cheers,
Grissiom
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] TeX Live 2014 #3 (third time's the charm?)
On Sun, Aug 17, 2014 at 2:45 PM, Robby Workman wrote: > On Fri, 4 Jul 2014 11:30:57 +0800 > Grissiom wrote: > > > On Thu, Jul 3, 2014 at 10:45 AM, Robby Workman wrote: > > > > > If something you need is missing from it, then make sure it's > > > present in the texlive-texmf-extra package. If not, then we have a > > > problem. If it is, then all is well, unless you have a really > > > strong case for why it should be included in the main texlive > > > package. > > > > > > > > I found the ctex package( http://www.ctan.org/pkg/ctex ) is in -extra > > but I think it's better in the main pkg since so many modern Chinese > > document is depend on the ctex classes and templates. > > > I'm inclined to accept this, but then I wonder if that's not a > too-slippery slope to consider. Is ctex included in the present > tetex stuff shipped with Slackware? In other words, if texlive > as packaged by my current scripts were added to Slackware today > (assuming the updmap.cfg bug mentioned elsewhere in this thread > is fixed now), would lack of ctex be a regression? > > Noop. CTex is not available in tetex because it highly depend on XeTeX to get the CJK fonts right. No, it won't considered as a regression if we don't include CTex(does tetex support CJK documents?). But since the total size of /usr/share/texmf-dist/tex/latex/ctex is only 221K, I think it will be a big win with little effort if we include it. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Abandoned build scripts
On Mon, Jul 7, 2014 at 3:03 PM, Robby Workman wrote: > I'm not sure if it's already been noted on the list or not (I've > done a horrible job of keeping up with email in recent months), > but vvoody has advised me privately that he's no longer using > Slackware and so all of his builds are free to good homes. > They are as follows: > misc/fcitx > misc/fcitx-configtool > misc/kcm-fcitx > So I would like the take the fcitx ones and > system/wqy-microhei-font-ttf > > the wqy fonts. = Moreover, I'd like to abandon some of my Slackbuilds: network/mldonkey libraries/libsunpinyin misc/ibus-pinyin misc/ibus-qt misc/ibus-sunpinyin misc/ibus development/generatorrunner development/sdcc Feel free to take them if you are interested. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] TeX Live 2014 #3 (third time's the charm?)
On Thu, Jul 3, 2014 at 10:45 AM, Robby Workman wrote: > Okay, I think I've got something that we can all accept, even if we're > not entirely happy with it. Please go forth and test. > > http://rlworkman.net/pkgs/sources/14.1/texlive-2014/ > rsync://rlworkman.net/rworkman/sources/14.1/texlive-2014/ > > As before, these links are not permanent, so if you find this in > a search engine, don't be surprised to see 404. :-) > > What I'd prefer is a test to see if your stuff works using *only* the > plain "texlive" package - that's the one that I'm hoping Pat will like > and be able to shoehorn into Slackware. > > If something you need is missing from it, then make sure it's present > in the texlive-texmf-extra package. If not, then we have a problem. > If it is, then all is well, unless you have a really strong case for > why it should be included in the main texlive package. > > I found the ctex package( http://www.ctan.org/pkg/ctex ) is in -extra but I think it's better in the main pkg since so many modern Chinese document is depend on the ctex classes and templates. The location of ctex in the -extra is: usr/share/texmf-dist/tex/latex/ctex/ -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] TeX Live 2014
On Tue, Jun 17, 2014 at 9:07 AM, Robby Workman wrote: > TeX Live 2014 has been released and I've found a bit of time to > do some preliminary testing, but before I upload it to SBo, I'd > like some more extensive testing from users. If some of you TeX > users would be so kind as to pull this and build it and then > test some of your .tex files to ensure that everything works as > expected, I'd greatly appreciate it. > > http://rlworkman.net/pkgs/sources/14.1/texlive-2014/ > rsync://rlworkman.net/rworkman/sources/14.1/texlive-2014/ > > What is the difference between the texlive-texmf-20140525.tar.xz located in your mirror and the official texlive-20140525-texmf.tar.xz ? I notice that the upstream texmf is 1.7GB and the Robby's one is just 544MB. So what did you strip out? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] SBo pyside upgrade
Hi all, As someone has noticed, the pyside packages are out of date and Chan is the first one come to tell me there should be an update. And I think Chan might be suitable for maintaining the scripts. So I would like to hand over the maintainer to him/her. The full conversion is attached below for reference. -- Cheers, Grissiom On Thu, Jul 25, 2013 at 12:43 AM, Kenneth Chan wrote: > Sure. I think I can handle it, although I'm a beginner in Python. > > So what's the hand over ritual? > > > On Tue, Jul 23, 2013 at 9:51 AM, Grissiom wrote: > >> Hi Chan, >> >> Thank you very much for using and improving that scripts. I'm no longer >> use these packages anymore and would you take maintainership of those? >> >> If all things are done, you can submit them in >> http://slackbuilds.org/guidelines/ and tell the admin the exchange of >> the maintainers. >> >> Thank you very much again. >> >> -- >> Cheers, >> Grissiom >> >> On Sun, Jul 21, 2013 at 10:03 PM, Kenneth Chan >> wrote: >> >>> Hi there. >>> >>> Recently I tried to install with sbopkg these packages: >>> >>> shiboken >>> pyside >>> pyside-tools. >>> >>> Since you're the maintainer of the packages I'd like to tell you that >>> the current build scripts no longer build the packages. I have updated the >>> .SlackBuild and .info scripts with the new links of the latest stable >>> version. >>> >>> I'm wondering what's the procedure to submit them to SBo. >>> >>> >>> Regards, >>> >>> Ken >>> >> ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] mendeleydesktop wrong md5
Hi Francesco Allertsen, On Sun, Aug 14, 2011 at 4:36 PM, Francesco Allertsen wrote: > Hi all, > > The md5sum of the 'mendeleydesktop' sources is wrong. > > The correct are those: > > x86: b4f6bd0e234d5d9e15d3354b99cb1473 > x86_64: dd9e485e2bb393b06c89ec85abb9a1b2 > > Please double check, but those should be the correct ones. > Yes, they are correct ones. But correct for version 1.0. And when you wget version 0.9.5.2 it will redirect(http 301) you to the version 1.0... mendeleydesktop has a tradition to do such kind of things... > If you want I can create the git patch that can be applied directly. > So the correct way is update the DOWNLOAD/VERSION/MD5SUM stuff, a whole version bump. BTW, if you are interested, feel free to take maintain of it. I don't use it daily any more. If not, I can do the version bump ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] virtualenv should belong to python/ ?
Hi all, virtualenv is a _tool_ to create isolated python env. So I think it belongs to python/, at least development/. What do you think? ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] fix Jinja2 typo
On Fri, Jun 24, 2011 at 5:08 PM, Mikko Varri wrote: > Thanks for pointing that out. > > Am I missing something? Instead of changing PRGNAM to PKGNAM > everywhere, a smaller patch would change one instance of PGKNAM to > PRGNAM. > > -cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs > $PKG/usr/doc/$PKGNAM-$VERSION > +cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs > $PKG/usr/doc/$PRGNAM-$VERSION > > PRGNAM is the right variable name for it, right? Oops, yeah, this patch is right. I thought is stands for "PaKaGe NAMe" at that time... Actually, it should be "PRoGram NAMe". -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] fix Jinja2 typo
This typo makes Jianja2 leave junk /usr/doc/-2.5.5 which does not make
sense to users.
Here is the patch
=
diff --git a/libraries/Jinja2/Jinja2.SlackBuild
b/libraries/Jinja2/Jinja2.SlackBuild
index 0a96b9d..b20307e 100644
--- a/libraries/Jinja2/Jinja2.SlackBuild
+++ b/libraries/Jinja2/Jinja2.SlackBuild
@@ -5,9 +5,9 @@
# Written by Mikko Värri (v...@linuxbox.fi)
# Public domain.
-PRGNAM=Jinja2
+PKGNAM=Jinja2
VERSION=${VERSION:-2.5.5}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
TAG=${TAG:-_SBo}
if [ -z "$ARCH" ]; then
@@ -20,7 +20,7 @@ fi
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
-PKG=$TMP/package-$PRGNAM
+PKG=$TMP/package-$PKGNAM
OUTPUT=${OUTPUT:-/tmp}
DOCS=${DOCS:-no}
@@ -30,9 +30,9 @@ set -e
rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
-rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
-cd $PRGNAM-$VERSION
+rm -rf $PKGNAM-$VERSION
+tar xvf $CWD/$PKGNAM-$VERSION.tar.gz
+cd $PKGNAM-$VERSION
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
@@ -49,13 +49,13 @@ fi
find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
-mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs
$PKG/usr/doc/$PKGNAM-$VERSION
-cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
+mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a docs/_build/html $PKG/usr/doc/$PKGNAM-$VERSION || cp -a docs
$PKG/usr/doc/$PKGNAM-$VERSION
+cat $CWD/$PKGNAM.SlackBuild > $PKG/usr/doc/$PKGNAM-$VERSION/$PKGNAM.SlackBuild
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cd $PKG
-/sbin/makepkg -l y -c n
$OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -c n
$OUTPUT/$PKGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
===
--
Cheers,
Grissiom
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] cardinal.lizella.net - help needed :/
2011/5/14 Ozan Türkyılmaz : > 2011/5/13 Robby Workman : >> > I`ll have to wait before I get my first wage. > Me too... -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] My SlackBuilds on -current.
On Sat, Apr 2, 2011 at 12:22 AM, Rich Shepard wrote: > On Fri, 1 Apr 2011, Greg' Ar Tourter wrote: > >> is R being picked up by anyone? otherwise I'll do it. it would be a >> shame to have that one unmaintained here. > > Greg, > > Ivan and I are newcomers to package maintenance but agreed to stumble > along together in maintaining R. Ivan's a chemist using R and I'm an > ecologist just learning R. > FYI, when I try to build R-2.13.0 with the old SlackBuild. I found some bugs: 1, --with-perl option is no longer needed. 2, the old SlackBuild didn't set the CXXFLAGS, FCFLAGS, FFLAGS and OBJCFLAGS. I doubt whether R actually use obj-c but configure report it. And it's no harm to set it. 3, "export" is needed in the "adjust PATH" line. With these changes applied, R seems build and run well on my system. I did a demo(graphics) and it went well. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] google-chrome
On Fri, Mar 25, 2011 at 11:56 AM, Erik Hanson wrote: > On Fri, 25 Mar 2011 00:42:45 -0300 > "Yucatan \"Kenjiro\" Costa" wrote: > >> Not to mention we can have google-chrome/chromium running without the >> need of some other dependencies like Orbit2 or Gconf. > > Repackaging the debian binary will continue to require these, and > eventually will require PAM as well. Yes, I think it will happen sooner or later. > I confirmed this recently by trying the unstable channel, at the time was > 11.0. The only answer I > can really think of here is to include some sort of pam-solibs type > package along with ORBit2/GConf. This is not a task I wish to > undertake, however. These days I simply compile chromium using your > script. :) > I think Slackware may include a fully functional PAM in the next release after 13.37(may be 14 or 14.xx?). As time goes by, PAM is more and more mature and is not the one years ago. Lots of distro have PAM and it is well tested in some degree. If we have PAM, building KDE might be easier too. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo
On Thu, Mar 10, 2011 at 2:24 AM, Eric Pratt wrote: > It was in the changelog. > > If you remove the '.' in 13.37, its like 'elite' in l33t speak. > Not mentioned in slackware64-current ChangeLog.txt tough... I think there is an other reason to be numbered as .37 -- RC1 use 2.6.37 kernel, which is going to be the kernel in next release. -- Cheers, Grissiom > On Wed, Mar 9, 2011 at 1:12 PM, Rich Shepard wrote: >> On Wed, 9 Mar 2011, Robby Workman wrote: >> >>> Okay, everybody saw the 13.37 rc1 announcement, >> >> First I've seen of it. >> >> Just curious why the version is 13.37 rather than 13.2. >> >> Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Web stats?
On Fri, Dec 17, 2010 at 9:47 PM, Erik Hanson wrote: > On Thu, 16 Dec 2010 17:38:24 -0400 > B Watson wrote: > >> A thought... Have been looking at some of the builds I submitted for >> 13.0 that didn't make it into the 13.1 repo (mostly because they need >> to be patched for 13.1's newer gcc). Going through them, patching, >> will eventually be resubmitting them, but I can't help but wonder >> whether some of the more niche-market ones are even being used > > I've never seen anyone complain that the site has too many scripts. > Yea, maybe I'm maintaining some niche-market scripts. But believe me, if YOU would like to use it, some one ELSE will use it too. SBo is worldwide and do have some influence. IMHO, there are enough audience. If it is true that the only one who use that SlackBuild is youself. Then it is no harm to upload it to SBo too. I think we can consider it as a backup. The more distributed, the safer the code is. This is not the purpose of SBo but I think it can be used like this. >> - A lot of users rsync the whole tree, and when they want to build >> something, just untar their copy of whatever.tar.gz from their local >> tree. > > Indeed. Approx. 9/10ths of our outgoing bandwidth is rsync data. There's > no realistic way to filter out what's being downloaded for the purposes > of build/install/use. > I used rsync to get thing up-to-date. But once the git repo is online, I switched to git. It can even show log, diff, branching... you name it ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] possible bug in laptop_mode
Hello all, In the official page of laptop_mode, the dev suggested add `/etc/rc.d/init.d/laptop-mode restart` in rc.local ( http://samwel.tk/laptop_mode/packages/slackware ). But the README in SBo's laptop_mode said we should add `/etc/rc.d/rc.laptop-mode start` in rc.local. i don't know which side is right... The reason of laptop_mode's dev is "Slackware doesn't completely clear /var/run on bootup". But after some investment in rc.S, we are cleaning /var/run (line 328 of that file). So what does "completely" there? Should we use "start" or "restart" in this case? Thanks. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] ipython pkg permission mistake
On Fri, Aug 27, 2010 at 10:43 AM, vvoody wrote: > ipython.Slackbuild > ... ... > # Install documentation: > mkdir -p $PKG/usr/doc > mv $PKG/usr/share/doc/ipython $PKG/usr/doc/ipython-$VERSION > chmod -R 0644 $PKG/usr/doc/$PKGNAM-$VERSION/* > ... ... > The 'chmod' line made the fault, which caused normal users not able to enter > into the directories of ipython-$VERSION/. > ll /usr/doc/ipython-0.10 > total 12 > drw-r--r-- 4 root root 4096 2010-08-27 09:56 examples/ > drw-r--r-- 2 root root 4096 2010-08-27 09:56 extensions/ > drw-r--r-- 3 root root 4096 2010-08-27 09:56 manual/ > Acutally, the permissions before makeing pkg are ok. So, maby that line is > no need, or using a better way instead. Yes, I can confirm this bug. Add the author as CC in case he/she is not in this list. Is there anything interesting in doc that should be kept away from normal users? ;) > Best regards. > -- > Free as freedom, slack as Slackware. > vvoody > -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] please reomve the ibus-qt in pending list
Hello admins, Sorry that I work out ibus-qt with old template. I will resubmit it once is was removed from pending. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Who's maintaining how many
On Tue, Aug 17, 2010 at 11:14 PM, Pierre Cazenave wrote: > I put the data in Calc and got it to run its (probably sketchy) regression. > It wouldn't fit an exponential curve, but the power curve worked nicely, > though gave an odd equation: 758.68x^-1.17 (negative power makes sense, > since it's a decreasing function). The correlation coefficient (r) is 0.97 > in this instance, which is pretty damned good. > > I've attached the figure, for those that way inclined. > > Pierre > Ha, great job! Does the data fit the 80/20 rule? ;D -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Who's maintaining how many
On Wed, Aug 18, 2010 at 3:13 AM, Grigorios Bouzakis wrote:
> On Tuesday 17 of August 2010 17:48:26 Binh Nguyen wrote:
>> Just curious among maintainers who's maintaining the largest packages,
>> I issued this command on my local SBo (get them with rsync)
>>
>> find SBo/13.1/ -name "*.info" -exec grep -H 'MAINTAINER' {} \; | cut
>> -d= -f2 | sort | uniq -c | sort -nr > maintainers.txt
>>
>> and the result
>>
>> http://pastebin.com/qF6k366M
>>
>> It's amazing that some guys like Robby and Erik can maintain over 100
>> packages! How could they manage to keep track of all their packages?
>>
>> Cheers,
>
> There is also pprkut with > 100 packages. He's listed at least 3 times as a
> maintainer with different aliases.
>
Yes, I'm "both" "Grissiom" and "grissiom" in the list. So I have 15
pkgs in the list ;)
--
Cheers,
Grissiom
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Add "unset CDPATH" at the head of SlackBuilds
Hello, In recent work, I know that it is better to unset CDPATH at the very beginning of packaging scripts. There are tow reasons: 1, If CDPATH is not empty, cd will echo the dir name to stdout each time changes pwd. This will mess up the output in some cases. 2, User can use CDPATH to mislead cd's search path and then _may_ do something dangerous. For example: ~/test$ pwd /home/grissiom/test ~/test$ cat t.sh export CDPATH="$HOME/test" cd $HOME echo "I'm at" $PWD cd test-cdpath echo "I'm at" $PWD "now" ~/test$ file ./test-cdpath/ ./test-cdpath/: directory ~/test$ file ~/test-cdpath/ /home/grissiom/test-cdpath/: directory ~/test$ sh t.sh I'm at /home/grissiom /home/grissiom/test/test-cdpath I'm at /home/grissiom/test/test-cdpath now You can see CDPATH can make cd don't change into folder under current directory. This may lead to vulnerable problems in SlackBuilds. This is tested in normal user but applicable to root. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20100629.1
On Tue, Jun 29, 2010 at 2:00 PM, Erik Hanson wrote: > Tue Jun 29 05:40:01 UTC 2010 ... > misc/sunpinyin: Added (Chinese input method) ... As I use sunpinyin as the main ibus engine, I may drop the maintain of ibus-pinyin. Anyone interested on it please feel free to take it over. Thanks ;-) If no one interested, I may do version bumps occasionally. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Grissiom, the content of panel.py in ibus 1.3.5 is not what it has to be.
On Fri, Jun 25, 2010 at 7:14 PM, Heinz Wiesinger wrote: > http://www.slackbuilds.org/submit/ > > Makes our live easier ;) > I think submit it through that way would be a duplicate thread of this one. But as you asked, I've done submitting the new package. Please check it. Thanks very much ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Grissiom, the content of panel.py in ibus 1.3.5 is not what it has to be.
On Fri, Jun 25, 2010 at 8:59 AM, Erik Hanson wrote: > On Fri, 25 Jun 2010 04:26:52 +0800 > Grissiom wrote: > >> On Wed, Jun 23, 2010 at 11:00 PM, Crocka Biscuit >> wrote: >> > I downloaded and viewed panel.py. >> > The content of panel.py was an HTML file describing panel.py. >> > It is not panel.py itself. >> > >> >> Hello Crocka Biscuit, >> >> Oops, I forgot to upload panel.py to SBo... Very sorry about this. The >> attachment should be the right package. Please use with it instead. >> >> I CC'ed to SBo list hoping that admins could pick it up too. >> >> Sorry for inconvenience... >> > > Can you submit a BUILD bump, it's a lot easier for us to handle. > Fixed. Hope this attachment will satisfy all the requirements ;-) -- Cheers, Grissiom ibus.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Grissiom, the content of panel.py in ibus 1.3.5 is not what it has to be.
On Wed, Jun 23, 2010 at 11:00 PM, Crocka Biscuit wrote: > I downloaded and viewed panel.py. > The content of panel.py was an HTML file describing panel.py. > It is not panel.py itself. > Hello Crocka Biscuit, Oops, I forgot to upload panel.py to SBo... Very sorry about this. The attachment should be the right package. Please use with it instead. I CC'ed to SBo list hoping that admins could pick it up too. Sorry for inconvenience... -- Cheers, Grissiom ibus.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Suggestion for packages which require a startup file.
On Sun, Jun 20, 2010 at 7:44 PM, Robert Kelsen wrote: > The proposed resolution to this issue: > > A simple symlink. > > Yes, a symlink (or series of symlinks). It can be included as part of the > package, and is removed if a package is uninstalled. > > Using our TiMidity++ example above, the symlink would point to > /etc/rc.d/rc.timidity and be located under /etc/rc.d/rc4.d. You could > call it S99timidity or something similar. I chose rc4.d, because it > makes sense that someone needing TiMidity++ would mainly use it in that > runlevel. It is a CLI-based tool, so you could add it to other runlevels > too. > I think one negative reason not to use it is that it is _possible_ that you start the service twice. For example, a user see the script in rc.d, and he knows that Slackware use BSD style init, so he add something like "/etc/rc.d/rc.timidity start" in rc.local without knowing that it is already started by the SystemV init compatible layer. So I think if a package mean to use SystemV style init, please drop the startup script into /etc/init.d/(which is a symlink to /etc/rc.d/init.d) and then symlink it to /etc/rc[0-6].d. I think the folder name says that "all the scripts under me are intended to be SystemV style init scripts." Anyway, my statement is not official at all ;-) But the positive reason to use your solution is that it is simple to end-user. Install and reboot(or manually do a startup), that's all. No need to edit files after install and uninstall. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20100612
On Sun, Jun 13, 2010 at 3:13 AM, Robby Workman wrote: > > On Sat, 12 Jun 2010 22:16:46 +0800 > Grissiom wrote: > > > On Sat, Jun 12, 2010 at 9:12 PM, Robby Workman > > wrote: > > > > > Sat Jun 12 12:50:05 UTC 2010 > > > > > ... > > > > > system/pyserial: Updated for version 2.5_rc2. > > > > > ... > > > > As the maintainer of pyserial in the time of 13.0, I didn't do version > > bumps. So does this mean that I lost the maintain? > > > No, that was my fault for not paying attention. I don't know if > I just missed the flagging for a maintainer change or if it did > not get flagged by our submit form (probably I just missed it), > but this update really shouldn't have happened. I have reverted > everything but the version bump, but if you don't want that > either, let me know and I'll revert that too. > > CC'ing Dustin on this to make sure he is aware. > > http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=08815b06853f4f > Yeah, that's OK. Actually when I submit the pyserial package, I know there is 2.5-rc2. But as it is considered as a RC, I _think_ it is not so mature to general usage. But Dustin may have his/her reason to do this update. Anyway, I think it is easy to roll back to the original version if something bad happend ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20100612
On Sat, Jun 12, 2010 at 9:12 PM, Robby Workman wrote: > Sat Jun 12 12:50:05 UTC 2010 > ... > system/pyserial: Updated for version 2.5_rc2. > ... As the maintainer of pyserial in the time of 13.0, I didn't do version bumps. So does this mean that I lost the maintain? Also, I noticed that the submission form is opened again. Congratulations ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [PATCH] misc/ibus: merge with new template and add kde4 integration
On Mon, Jun 7, 2010 at 2:23 PM, Robby Workman wrote: > > Well, back to the "Pat" argument, but he prefers to use "cp -a" > for those so that the original timestamps will be preserved -- > it can be handy to know just how old a doc is when you're reading > it... > > I think that's a very wonderful reason ;-) We have `chown -R root:root` and `find . ... -exec chmod ..` stuffs so there won't be permission issues. Excellent match :D If we want to copy something outside the source ball we still have to play the cat trick I think. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [PATCH] misc/ibus: merge with new template and add kde4 integration
On Sun, Jun 6, 2010 at 11:35 PM, wrote: > cp preserves some file modes this is bad because it depends on the source > file having correct permissions. > > # cp test test3 > [r...@slacker:/home/gizzmo/test] > # ls -l > total 0 > -rwxrwxrwx 1 root root 0 2010-06-06 10:59 test > -rwxr-xr-x 1 root root 0 2010-06-06 11:01 test3 > > This is correct according to the doc(minus umask which is usually 022). I admit this is a little bit magic in some condition. > cp -a preserves ownership and permissions, this is also bad because it > depends on the source file having the correct ownership and permissions. > # cp -a test test5 > [r...@slacker:/home/gizzmo/test] > # ls -l > total 0 > -rwxrwxrwx 1 nobody root 0 2010-06-06 10:59 test > -rwxrwxrwx 1 nobody root 0 2010-06-06 10:59 test5 > > cp can be made to work as we need it to but it takes a long list of flags > and in the end works no better than the simple cat something > somewhere. Thanks for the detailed explanation. Then I know I should have a look at the ap -a in my SlackBuilds(template use it to copy docs) ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [PATCH] misc/ibus: merge with new template and add kde4 integration
On Sun, Jun 6, 2010 at 1:49 PM, JK Wood wrote: > > Permissions. cp can misbehave where cat won't. > > Hmm, could you give concrete examples? In `info coreutils 'cp invocation'`: In the absence of this option, each destination file is created with the mode bits of the corresponding source file, minus the bits set in the umask and minus the set-user-ID and set-group-ID bits. *Note File permissions::. AFAIK, cat + > will create a file in "default mode", which is masked by umask. Originally, umask is set to 022. But who knows what would happen after the system run for years? ;-) IMHO, cp will preserve file modes in some degree while cp + > will create files in "default mode". Feel free to correct me if I have something wrong. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [PATCH] misc/ibus: merge with new template and add kde4 integration
On Sun, Jun 6, 2010 at 12:38 PM, Robby Workman wrote: > > NAK on change to README - notify-python is part of Slackware. > > Oops, I didn't notice that. Thanks for fixing it. > A few tweaks to the other stuff, but applied at commit id > bfe9c28b08e6288beb8bc6086f849ecd8b3af38a in my branch. > > Thanks a lot for other cleanups. But it seems that you prefer cat rather than cp(You changed `cp $CWD/panel.py $PKG/usr/share/ibus/ui/kimpanel/` to `cat $CWD/panel.py > $PKG/usr/share/ibus/ui/kimpanel/panel.py` in this case). May I know the reason? ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [PATCH] misc/ibus: merge with new template and add kde4 integration
Hello *
I can't wait for the submission to open so I backported the updates of ibus
to 1.3.1 which is the current version in SBo tree. So I hope the patch this
time can be considered as "minor updates and fixes" ;-)
The attachment is the output of git format-patch. The only problem I found
is it will generate diff in the APPROVED entry of .info file, which is
obviously useless in our case...
I will do version bump when the submission open again.
--
Cheers,
Grissiom
From b7772d6fc145b243e15b6cfac4afbdbb8ce67bfd Mon Sep 17 00:00:00 2001
From: Grissiom
Date: Sun, 6 Jun 2010 10:44:12 +0800
Subject: [PATCH] misc/ibus: merge with new template and add kde4 integration
---
misc/ibus/README |2 +-
misc/ibus/README.SBO |8
misc/ibus/doinst.sh | 18 --
misc/ibus/ibus.SlackBuild | 22 --
misc/ibus/ibus.info |2 +-
5 files changed, 38 insertions(+), 14 deletions(-)
diff --git a/misc/ibus/README b/misc/ibus/README
index e1265f0..bffe100 100644
--- a/misc/ibus/README
+++ b/misc/ibus/README
@@ -6,7 +6,7 @@ After installing at least one engine (e.g. PinYin engine) and enabling it
in ibus-setup, ibus itself should be fully functional. If you want to use
ibus as your primary input method, you should remove the scim package.
-This requires gconf and pyxdg.
+This requires gconf, notify-python and pyxdg.
If you use qt applications, then you probably want ibus-qt as well.
After installing, ibus will automatically be started in an xdg-compliant
diff --git a/misc/ibus/README.SBO b/misc/ibus/README.SBO
index a7c2378..5521d56 100644
--- a/misc/ibus/README.SBO
+++ b/misc/ibus/README.SBO
@@ -25,3 +25,11 @@ chmod +x /etc/profile.d/ibus.{sh,csh} will enable environment variable settings
at login, but if you have ibus-qt installed, you may also prefer to run
qtconfig and set "Default Input Method" to ibus.
+=
+integration with KDE4
+=
+Add ``--panel=/usr/share/ibus/ui/kimpanel/panel.py`` parameter to ibus when you
+run ibus-daemon. For example, you can append it to the "Exec" entry in
+/etc/xdg/autostart/ibus.desktop or any .desktop file you created for launching
+ibus. Then add "kimpanel" plasmaiod to your panel or dashboard. Restart ibus,
+you will see it shining out there.
diff --git a/misc/ibus/doinst.sh b/misc/ibus/doinst.sh
index b292e62..d05ce7f 100644
--- a/misc/ibus/doinst.sh
+++ b/misc/ibus/doinst.sh
@@ -11,6 +11,17 @@ config() {
# Otherwise, we leave the .new copy for the admin to consider...
}
+preserve_perms() {
+ NEW="$1"
+ OLD="$(dirname $NEW)/$(basename $NEW .new)"
+ if [ -e $OLD ]; then
+cp -a $OLD ${NEW}.incoming
+cat $NEW > ${NEW}.incoming
+mv ${NEW}.incoming $NEW
+ fi
+ config $NEW
+}
+
GCONF_CONFIG_SOURCE="xml::etc/gconf/gconf.xml.defaults" \
chroot . gconftool-2 --makefile-install-rule \
/etc/gconf/schemas/ibus.schemas 1>/dev/null
@@ -27,12 +38,7 @@ fi
# Prepare the new configuration files
for file in etc/profile.d/ibus.sh.new etc/profile.d/ibus.csh.new ; do
- if [ -e $(dirname $file)/$(basename $file .new) -a -x $(dirname $file)/$(basename $file .new) ]; then
-chmod 0755 $file
- else
-chmod 0644 $file
- fi
- config $file
+ preserve_perms $file
done
# Run gtk-query-immodules so that "ibus" will appear under Input Method
diff --git a/misc/ibus/ibus.SlackBuild b/misc/ibus/ibus.SlackBuild
index e0bad2c..1d31a03 100644
--- a/misc/ibus/ibus.SlackBuild
+++ b/misc/ibus/ibus.SlackBuild
@@ -32,7 +32,6 @@ VERSION=${VERSION:-1.3.1}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
-# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
@@ -71,10 +70,10 @@ tar xvf $CWD/${PRGNAM}-${VERSION}.tar.gz
cd ${PRGNAM}-${VERSION}
chown -R root:root .
find . \
- \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
- -exec chmod 755 {} \; -o \
- \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
- -exec chmod 644 {} \;
+ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
+ -exec chmod 755 {} \; -o \
+ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
+ -exec chmod 644 {} \;
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
@@ -89,6 +88,17 @@ CXXFLAGS="$SLKCFLAGS" \
make
make DESTDIR=$PKG install
+# add kimpanel support, panel.py is harvested from
+# http://websvn.kde.org/tags/KDE/4.4.3/kdeplasma-addons/applets/kimpanel/backend/ibus/panel.py
+mkdir $PKG/usr/share/ibus/ui/kimpanel
+cp $CWD/panel.py $PKG/usr/share/ibus/ui/kimpanel
+# make sure panel.py is executable.
+chmod +x $PKG/usr/share/ibus/ui/kimpanel/panel.py
+# link the icon to where kimpanel will look for.
+( cd $PKG/usr/share/ibus/icons
+ ln -s ../../ico
Re: [Slackbuilds-users] updates of the SlackBuilds maintained by me
On Tue, Jun 1, 2010 at 2:26 PM, Robby Workman wrote: > On Sun, 30 May 2010 20:11:28 +0800 > Grissiom wrote: > > > My updates of the SlackBuilds is here: > > > > http://github.com/grissiom/slackbuilds (or git url, git:// > > github.com/grissiom/slackbuilds.git) > > > > Main changes are update with upstream and merge with new templates. I > > think a git log -p will show all the stuffs ;-) > > > > Hope they could be merged into the mainline. If have any problem, > > feel free to contract with me. > > > pyserial is 450fde1509106c6beafe0d030d523b5fee7b5445 in my branch. > > The others are version bumps, so they'll have to wait for the > submission form to open again. > > Hmm, thanks for the clarify. Then I got to know version bump isn't minor stuff ;) I will wait for the submission form for the rest of updates. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] updates of the SlackBuilds maintained by me
Hello, My updates of the SlackBuilds is here: http://github.com/grissiom/slackbuilds (or git url, git:// github.com/grissiom/slackbuilds.git) Main changes are update with upstream and merge with new templates. I think a git log -p will show all the stuffs ;-) Hope they could be merged into the mainline. If have any problem, feel free to contract with me. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] ibus-anthy
2010/5/29 Ozan Türkyılmaz > it turns out i and bash screwed up. > Hmm? It is the ibus-qt.SlackBuild screwed up your bash or some else? From the error message in the original post, it looks like a ARCH issue: set it to x86_64 if you are running 64bit slackware. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo?
On Sat, May 29, 2010 at 12:32 AM, xgizzmo wrote: > I don't not speak for the whole admin staff. But I feel it is almost > pointless to try and maintain anything based on -current. You will > expend tons of time doing it, and run the risk of having everything > you worked on being undone by a single up date to -current. If we made > a -current repo then we would be forced into keeping it up to date > with -current, something I do not intend to do. > Hmm, that's a good reason. For the seek of ease of maintain and stability, I agree with you. So it seems that I have to keep a stable release of Slackware to maintain my SlackBuilds, which will cancel out my desire to track -current ;( -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Will there be a "current" branch in official SBo git repo?
Hello all, It's exciting to hear and see that SBo team have a public git repo now(You have SCM finally ;-). It is very good for cooperating. Although it's a little earlier, I just wonder, will there be a "current" branch that oriented to -current ? Ponce has a repo dedicated for -current ( http://github.com/Ponce/SBo-git ) but that's a different repo and the SBo one is much more cleaner. I think -current users will be very happy if SBo has a current branch and it could collect more work from them. What do you think? ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] ibus-anthy
2010/5/28 Ozan Türkyılmaz > > by the way ibus-qt fails at compile time. it complains that gcc can't > even compile > a simple test program. i tried latest one from the ibus project, too. > > Hmm, really? ibus-qt compile and run happily on my box(slackware13.1-64bit) Anyway, you can get the "current" version from here: http://gitorious.org/~grissiom/slackbuilds/grissioms-clone/trees/master/ibus-qt I haven't update it to the lastest template yet. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20100517
2010/5/18 Antonio Hernández Blas > Some VERSION mismatch between info and SlackBuild files: > > misc/heyu >VERSION value in info file is: '2.4.0' >But VERSION value in SlackBuild file is: '2.8.0' > > ... > network/r2e >VERSION value in info file is: '2.6.6' >But VERSION value in SlackBuild file is: '2.66' > > network/knock >VERSION value in info file is: '.0.5' >But VERSION value in SlackBuild file is: '0.5' > > network/dnstop >VERSION value in info file is: '20080502' >But VERSION value in SlackBuild file is: '20090128' > > I think it's impossible to find all the mismatches by hand. So did you use a script or something like that to check them? I'm curious about this because the job is much like what my little project should do -- sbo-dev-helper ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Drop some package maintenance of mine
On Tue, Apr 27, 2010 at 10:58 PM, Greg' Ar Tourter wrote: > Hi Grissom, > > I can take over cuetools if you want. > > Thanks! I'm glad someone would take care of it. Just take it over ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Drop some package maintenance of mine
2010/4/27 João Felipe Santos > Hello, > > I can keep sympy updated. I would update it for using it on my > machines, anyways :) > > Thanks! I noticed there is new version of sympy but as I don't use it anymore, I didn't update it. Just take it over ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Drop some package maintenance of mine
On Tue, Apr 27, 2010 at 6:13 PM, LukenShiro wrote: > > I would take care of "pycurl" and "Pygments" > > > Thanks a lot. ;-) -- Take care, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Drop some package maintenance of mine
Hello all, Because I don't use them now, I want to hand over some package maintenance: pycurl Pygments sympy zsync cuetools I would be glad to see these packages having new maintainers. If not, I *may* keep bumping the versions. But I cannot guarantee these packages are all up-to-date and working. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Something about my ibus-*.SlackBuids
Hello all, 1, ibus-1.3.0 is finally out and I have submitted new SlackBuild for it. If anyone can wait it to be approved, please pull the new one from http://gitorious.org/~grissiom/slackbuilds/grissioms-clone/trees/master/ibus. Note that the new version have a new dependency -- notify-python. 2, I don't want to upgrade ibus-pinyin now because it have a new dependency -- libsigc++. Although it can be found in SBo but I don't even want to have a try for it. The reason is simple: the current version(1.2.99.20100202) works fine, even with ibus-1.3.0. If anyone think I should upgrade ibus-pinyin, please drop me a comment. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] the .info file
On Fri, Feb 26, 2010 at 8:25 AM, JK Wood wrote: > The day SBo starts tracking dependencies is the day I fork the project... > > Wait, I already forked the project... > > Okay, so the day SBo starts tracking dependencies is the day I stop > submitting SlackBuilds. > > --JK > > Hi, don't be so hurry~;) I don't think the admins will accept this proposal(to add dependency lines in .info) simply because Slackware doesn't have it. Users always have an attempt to automate every thing(including me sometimes). But in my _own_ view, slackware's philosophy is `program is bullsh*t, manage them by yourself`. Actually, there is a place to tell user dependencies -- README. However, there is even no very-machine-friendly 'format' to declare that. IMHO, it force users to read them by their own before making any packages. Just my two cents. ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Some dead link
On Wed, Feb 17, 2010 at 12:47 AM, Zordrak wrote: > Murat D. Kadirov wrote: > > Hmm.. What about version 2.1.0.81? It does not work in slackware 13? > > > > I tried it on Slack64-current with Multilib and it just segfaulted on > me. I don't know what anyone else's experience is. > Same here. I could launch the shared version. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Some dead link
On Wed, Feb 17, 2010 at 12:39 AM, Murat D. Kadirov wrote: > Hmm.. What about version 2.1.0.81? It does not work in slackware 13? > > Hmm.. I can launch it in slackware64-current-multilib. But I haven't fully test it because it may take time to know how to play with it... -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Some dead link
On Tue, Feb 16, 2010 at 11:59 PM, Zordrak wrote: > > > The link was moved from skype to an external site. It works fine. > > Oops, I'm sorry. You are right. I failed to get the file from the original site(inside skype.com). It gave me the impression that the link on SBo was dead... Sorry for disturbing. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Some dead link
On Tue, Feb 16, 2010 at 11:49 PM, Heinz Wiesinger wrote: > On Tuesday 16 February 2010 16:27:58 Grissiom wrote: > > Hi all, > > > > I found some dead links: > > > >[..] > > > > 2, skype. Seems the 2.1.0.81 released and the devs removed the link to > old > > version... ;( > > I fixed this last week. Try updating the script from our repo. > > Oh, my local copy is up-to-date. See: http://slackbuilds.org/repository/13.0/network/skype/ -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Some dead link
On Tue, Feb 16, 2010 at 11:37 PM, Aleksandar Samardzic wrote: > > They've pulled it in the meantime, here is the notice from SciPy site: > "NumPy 1.4.0 release pulled. (2010-2-8) Due to an unintended ABI break > the 1.4.0 release has temporarily been pulled pending a decision on > how to handle the ABI incompatibility." > > What a pity > I'm not sure what to do here - if there is backup of 1.3.0 SlackBuild, > then I guess it should be brought back; otherwise, I could prepare it > again. > If you can play with git, you can get your scripts back from: http://github.com/Ponce/SBo-git otherwise, maybe the admins have some magic to get we back to the Good Old Days... ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Some dead link
Hi all, I found some dead links: 1, numpy. In http://sourceforge.net/projects/numpy/files/ , it seems that there is no 1.4.0 release and wget got "404 not found " when I want to download the 1.4.0 tarball 2, skype. Seems the 2.1.0.81 released and the devs removed the link to old version... ;( -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] './configure' return 1 but make and works well
./configure || true will do the trick. But I just wonder why the configure will fail. Maybe a talk to the devs is needed. ;( On Sat, Feb 13, 2010 at 4:00 PM, vvoody wrote: > I'm building the slackbuild for fbterm-1.6. > With build script a little modified from fbterm-1.5(just version > infomation), I found that > the building process exited after 'configure'. It didn't do the make. Then > I checked the 'config.log', > there is one unsual line in it: > > """ > r...@slackware:/tmp/SBo/fbterm-1.6# tail -3 config.log > #define HAVE_SIGNALFD 1 > > configure: exit 1 > r...@slackware:/tmp/SBo/fbterm-1.6# > """ > > So, I built fbterm-1.6 manually. After './configure', the command 'echo $?' > returned 1. > The 'config.log' file was same as above. The configure process didn't show > any errors. > > Finally, I commented the 'set -e' line the fbterm.SlackBuild and finished > building the package. > And the fbterm program works well. > > I wonder if there is another way to work around this, not commenting the > 'set -e' line. > > Best regards! > -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20100210
On Thu, Feb 11, 2010 at 6:14 AM, wrote: > > Wed Feb 10 21:45:01 UTC 2010 > ... > misc/ibus: Updated for version 1.2.99.20100202. > Thanks to Grissiom. --dsomero > ... Thanks for the hard working of the admins. For those who upgrade ibus to this version. Please note that ibus has changed it's so lib version. After upgrading, all the engines(or at least ibus-pinyin) need to be rebuild and upgrade. I wish this won't trouble you too much. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Error msg shown when installing mozilla-nss
Hi all, When I install mozilla-nss I encountered some error messages. I don't know the reason nor how to deal with it. It will be very kind of you if someone could help: Verifying package mozilla-nss-3.12.4-x86_64-1_SBo.txz. Installing package mozilla-nss-3.12.4-x86_64-1_SBo.txz: PACKAGE DESCRIPTION: # mozilla-nss (Network Security Services) # # Network Security Services (NSS) is a set of libraries designed to # support cross-platform development of security-enabled client and # server applications. Applications built with NSS can support # SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, # X.509 v3 certificates, and other security standards. # # Read http://www.mozilla.org/projects/security/pki/nss/overview.html # /sbin/ldconfig: /usr/lib64/libplds4.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libssl3.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libnssutil3.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libnspr4.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libplc4.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libsmime3.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libnss3.so is not a symbolic link Executing install script for mozilla-nss-3.12.4-x86_64-1_SBo.txz. /usr/lib64/pkgconfig /usr/lib64/pkgconfig /usr/lib64/pkgconfig /usr/lib64/pkgconfig Package mozilla-nss-3.12.4-x86_64-1_SBo.txz installed. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] experimenting with git
On Sun, Jan 31, 2010 at 7:17 PM, Matteo Bernardini wrote: > hi fellas, > > looking for a way to manage building from current with sbopkg and mantain a > modified slackbuilds.org repository I tried to use it with git. > I pulled yesterday's repo and started doing tags for the build scripts I > modified for clean build on current and then I merged them all. > This is the patch I use (made with git diff from the first commit) against > slackbuilds.org 13.0 repo > > http://ponce.pastebin.com/f70344f2a > > and this is the git repo itself > > http://github.com/Ponce/SBogit > > gotta say git is fun :D > > I'm interested with the idea -- use git to track a "branch" of SBo repo. Actually, I(together with vvoody) have a git repo to track our SlackBuilds: http://gitorious.org/slackbuilds I'm also interested in how do the SBo admins do source control management ;) SVN, or just tarball backups? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN] sbo-dev-helper 0.0.5
On Sat, Jan 16, 2010 at 7:06 PM, Grissiom wrote: > Hello all, > > After long period of time, here comes version 0.0.5 of sbo-dev-helper. Main > changes are: > 1, fix a typo in configuration name.(~/.sbo-dev-helver.cfg => > ~/.sbo-dev-helper.cfg) > Please rename your configuration. Sorry for inconvenience. > Thank Greg' Ar Tourter for bug report. > 2, parse -h option before checking SBO_* envs. This could let the use see > help doc even without configurations. Thank Greg' Ar Tourter > 3, adjust the right place after replacing the appnam Thank Greg' Ar > Tourter > 4, add doinst.sh in default. Thank Greg' Ar Tourter. > 5, new template files saved as .new files in $SBO_TEMPLATES. > 6, Many doc improvements. > > Many of them have usability improvements. Please update your local package. > Sorry that I forgot the download link: http://sbo-dev-helper.googlecode.com/files/sbo-dev-helper-0.0.5.tar.gz Hope you would like this new version ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [ANN] sbo-dev-helper 0.0.5
Hello all, After long period of time, here comes version 0.0.5 of sbo-dev-helper. Main changes are: 1, fix a typo in configuration name.(~/.sbo-dev-helver.cfg => ~/.sbo-dev-helper.cfg) Please rename your configuration. Sorry for inconvenience. Thank Greg' Ar Tourter for bug report. 2, parse -h option before checking SBO_* envs. This could let the use see help doc even without configurations. Thank Greg' Ar Tourter 3, adjust the right place after replacing the appnam Thank Greg' Ar Tourter 4, add doinst.sh in default. Thank Greg' Ar Tourter. 5, new template files saved as .new files in $SBO_TEMPLATES. 6, Many doc improvements. Many of them have usability improvements. Please update your local package. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN]: sbo-dev-helper 0.0.4
On Sun, Jan 3, 2010 at 4:45 AM, Greg' Ar Tourter wrote: > Hi Grissiom > > Thanks for the great work. > > One thing I have noticed is that the configuration file is mispelt > (well I think it is but it is due to the way it was spelt in the > original suggestion.) > > ~/.sbo-dev-helver.cfg instead of ~/.sbo-dev-helper.cfg > > Also, calling the scripts with -h without the SBO_TEMPLATES variable > set, just gives the message that it should be, rather than the full > help. > Thanks for pointing out these bugs! ;) I fixed them in the snapshot(attachment). You can have a try if you want. ;) If you have anymore about the little program, feel free to tell me ;-) -- Cheers, Grissiom sbo-dev-helper-snapshot.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [ANN]: sbo-dev-helper 0.0.4
Hello all, Happy New Year! As a gift, I will announce version 0.0.4 of the little sbo-dev-helper which can be downloaded from http://sbo-dev-helper.googlecode.com/files/sbo-dev-helper-0.0.4.tar.gz . The main differences from previous versions are: *, Added diff_sbo script to show the diff between your working copy and the one in official repo.(This require a rsync(or equivalent) local copy of official repo) *, doc updates including new INSTALL instruction. *, directory re-structure. *, build utilities enhancements. *, adapted to utilize http://slackbuilds.org/templates/ (Thanks to the SBo admins!) *, some bug fixes and improvements. As always, suggestions and patch are strongly welcomed! ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Mendeley source links dead
On Mon, Dec 28, 2009 at 2:03 PM, Grissiom wrote: > On Mon, Dec 28, 2009 at 7:19 AM, Morten Juhl-Johansen Zölde-Fejér > wrote: >> I am afraid the links to the source files of Mendeley at >> http://slackbuilds.org/repository/13.0/academic/mendeleydesktop/ are >> broken. >> > > Try these please: > http://www.mendeley.com/downloads/linux/mendeleydesktop-0.9.4.1-linux-i486.tar.bz2 > http://www.mendeley.com/downloads/linux/mendeleydesktop-0.9.4.1-linux-x86_64.tar.bz2 > > I think the reason they changed the link is there is a new release... > If you launch 0.9.4.2(the one supported by my SlackBuild), it will > promote you to upgrade. But unless you are root, there is no hope to > accomplish that. And DO NOT upgrade! I don't know the consequences it > will cause... > > I will submit a new SlakckBuild for it soon. New SlackBuild in the attachment, for those who cannot to wait;-) Note, it has no been approved by the admins yet. So use with your own risk. -- Good Luck, Grissiom mendeleydesktop.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Mendeley source links dead
On Mon, Dec 28, 2009 at 7:19 AM, Morten Juhl-Johansen Zölde-Fejér wrote: > I am afraid the links to the source files of Mendeley at > http://slackbuilds.org/repository/13.0/academic/mendeleydesktop/ are > broken. > Try these please: http://www.mendeley.com/downloads/linux/mendeleydesktop-0.9.4.1-linux-i486.tar.bz2 http://www.mendeley.com/downloads/linux/mendeleydesktop-0.9.4.1-linux-x86_64.tar.bz2 I think the reason they changed the link is there is a new release... If you launch 0.9.4.2(the one supported by my SlackBuild), it will promote you to upgrade. But unless you are root, there is no hope to accomplish that. And DO NOT upgrade! I don't know the consequences it will cause... I will submit a new SlakckBuild for it soon. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] About the http://slackbuilds.org/templates/
On Sat, Dec 26, 2009 at 10:07 AM, Michiel van Wessem wrote: > you mean like: > > http://slackbuilds.org/templates/template.info > Yup! That's what I'm talking about! Thanks! ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091221
On Sat, Dec 26, 2009 at 4:14 AM, Robby Workman wrote: > That would be *my* fault. My workflow on approvals is such > that I have to manually replace newer submissions in my local > pending queue if one was already there. Guess what? I forgot > this time :-) Never mind~ I will re-submit it. ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] About the http://slackbuilds.org/templates/
2009/12/25 Niklas 'Nille' Åkerström : > Grissiom skrev 2009-12-25 11:17: >> >> Hello admins, >> >> First of all, Big Thanks to the open admins that make >> http://slackbuilds.org/templates/ online. Thanks for caring the >> end-users~;) >> >> However, it *seems* that the template.info is missing. >> >> Thanks again for caring this. >> >> > > No it's not missing. > http://slackbuilds.org/guidelines/ > There you will find "The $PRGNAM.info file" > /Nille Yes, one can scroll down the page and extract the content of info file among other hundreds of words. But I think it may be more convenience that provide a "dry" template info file there. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] About the http://slackbuilds.org/templates/
Hello admins, First of all, Big Thanks to the open admins that make http://slackbuilds.org/templates/ online. Thanks for caring the end-users~;) However, it *seems* that the template.info is missing. Thanks again for caring this. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091221
On Tue, Dec 22, 2009 at 12:12 AM, Robby Workman wrote: > Mon Dec 21 16:09:47 UTC 2009 > misc/ibus-qt: Updated for version 1.2.0.20091206. > Thanks to Grissiom. --rworkman I'm so sorry that the latest version(and the one works better) of ibus-qt should be 1.2.0.20091217. I remember I asked the admins to remove ibus-qt in the old pending and re-submitted the new one. But I've no idea that why and how could I submitted the wrong version. I will re-submit it soon. Sorry for inconvenience... -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Please substitute ibus-qt in the pending queue with the attachment
Hello, The author of ibus-qt didn't test his previous release So maybe this one could be better for the public. Sorry for inconvenience. -- Cheers, Grissiom ibus-qt.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN]: sbo-dev-helper project
On Thu, Dec 17, 2009 at 7:42 AM, Niels Horn wrote: > > Some more suggestions... (hey, you asked for it :D ) > 1) config file > > Instead of entering mu name & e-mail every time (they don't change > that much), save them in a file called /etc/sbo-dev-helver.cfg > > 2) template.info / slack-desc.template > > It was not very clear what should be in these files, but I think I > managed to build them by reading the scripts. > > 3) new_pkg > - It warns when "approved" is not set, but AFAIK it shouldn't > - The md5sum check does not always work. Some download links simply do > not end with the filename... :( So I guess this should be a warning, > not an error > - I think the solution to add files can be improved. I have several > SlackBuilds with extra files (patches / README.Slackware / etc.). I > suggest adding everything to the tarball, *except*: *.tar.?g* / *~ / > > Hello Niels Horn and anyone interested, I implemented all the suggestions except for the last one which is still in hot debate and pushed my local changes to gitorious. And guys, maybe I won't have enough time to heavily develop it in the following month. I have to prepare for a examination hold in 9th, Jan 2010. However, I will follow any discussions here and anyone can create an "Issue" in http://code.google.com/p/sbo-dev-helper/issues/list where I will check after the examination. Thanks for everyone participated~ ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN]: sbo-dev-helper project
On Thu, Dec 17, 2009 at 12:43 PM, Robby Workman wrote: > > Use printf instead if you need portability. > > > Thanks for the advise. I will go through the scripts to see whether there are other places need printf. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN]: sbo-dev-helper project
On Thu, Dec 17, 2009 at 7:42 AM, Niels Horn wrote: > > > Some more suggestions... (hey, you asked for it :D ) > > Yup, really thanks for the patches and suggestions! ;D It's too late last night so I sent the mail and then went to bad and have been sleeping till noon ;( > 1) config file > > Instead of entering mu name & e-mail every time (they don't change > that much), save them in a file called /etc/sbo-dev-helver.cfg > > Good idea. But instead of a system wide configuration, I prefer a per-user configuration. Could ~/.sbo-dev-helver.cfg be ok? > 2) template.info / slack-desc.template > > It was not very clear what should be in these files, but I think I > managed to build them by reading the scripts. > > When I wake up in the noon I realized that I didn't doc what these files are... ;( I will add a description somewhere. And for sbo admins, would you like to add a folder to contain all the template files(slack-desc, info, SlackBuild) somewhere like ftp://ftp.slackbuilds.org/templates ? Then it will be very convenient for users to follow the changes. I remember I missed the info changes when 13.0 was out ;) > 3) new_pkg > - It warns when "approved" is not set, but AFAIK it shouldn't > Hmm, yes, this is a problem. > - The md5sum check does not always work. Some download links simply do > not end with the filename... :( So I guess this should be a warning, > not an error > Hmm, yes, reasonable. > - I think the solution to add files can be improved. I have several > SlackBuilds with extra files (patches / README.Slackware / etc.). I > suggest adding everything to the tarball, *except*: *.tar.?g* / *~ / > > Hmm, my hobbit is untar the source in the working directory and have a look at it and write/modify the SlackBuild etc. And the working dir maybe really dirty -- have log files, swp files, and other files that shouldn't be in the tarball. So I prefer the "white list" approach than the "black list" approach. What do you think? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [ANN]: sbo-dev-helper project
On Thu, Dec 17, 2009 at 7:09 AM, Niels Horn wrote: > Grissiom, > > The update_sbo_tpl does not use the SBO_TEMPLATES variable all the > way, and echo "\t" does not work correctly in bash. > > I patched the file like this: > > --- sbo-dev-helper/usr/bin/update_sbo_tpl2009-12-16 21:03:45.0 > -0200 > +++ /usr/bin/update_sbo_tpl2009-12-16 21:01:56.0 -0200 > @@ -7,12 +7,12 @@ > > wget http://www.slackbuilds.org/template.SlackBuild -O > $SBO_TEMPLATES/template.SlackBuild.new > > -if [ "$(cat templates/template.SlackBuild | md5sum -)" \ > -!= "$(cat templates/template.SlackBuild.new | md5sum -)" ]; then > -echo "\ttemplate.SlackBuild have changed!!!" > -echo "\tConsider update your SlackBuilds!" > -echo "\tNew template file restored as > $SBO_TEMPLATES/template.SlackBuild.new" > +if [ "$(cat $SBO_TEMPLATES/template.SlackBuild | md5sum -)" \ > +!= "$(cat $SBO_TEMPLATES/template.SlackBuild.new | md5sum -)" ]; then > +printf "\ttemplate.SlackBuild have changed!!!" > +printf "\tConsider update your SlackBuilds!" > +printf "\tNew template file restored as > $SBO_TEMPLATES/template.SlackBuild.new" > exit 1 > else > -rm templates/template.SlackBuild.new > +rm $SBO_TEMPLATES/template.SlackBuild.new > fi > > Oops, I forgot to change them Thanks for catching it. I will fix it when my slackware box can get online... For shell, I use zsh as my primary shell... Thanks for testing it in other environments. Will `echo -e "\t..."` be ok? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [ANN]: sbo-dev-helper project
Hello everyone, I did a little project named sbo-dev-helper which contain helper scripts that ease your dev progress for SBo. Project hosted in: http://gitorious.org/sbo-dev-helper It have 3 scripts by now: new_SlackBuild: A script to establish a new SlackBuild working directory. new_pkg A script that create a tarball that you intent to submit to SBo. update_sbo_tpl A script that get template updates from SBo and notify you if there is any. Hope they could be helpful. Any suggestions or patches are welcome ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Testing utf8...
On Wed, Dec 16, 2009 at 14:59, Robby Workman wrote: > On Wed, 16 Dec 2009 06:57:30 + > Robby Workman wrote: > > > Okay, I *think* we (rob0 and I) figured out at least part of the > > problem after some testing in various scenarios. It seems that > > mutt (and pine and mailx and pretty much anything else) when run > > in screen shows (and sends) garbled utf8. > > > > After adding this line to $HOME/.screenrc: > > defutf8 on > > > > and restarting screen completely (kill it dead and start over, > > thereby losing all the precious IRC chatter) ;-) it seems to > > work. Here's hoping this mail won't prove me wrong. > > > > Here goes: Ozan Türkyılmaz > > > Yay! :-) > > Congratulations! -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091206
2009/12/7 Ozan Türkyılmaz > 2009/12/7 Grissiom : > > 2009/12/7 Ozan Türkyılmaz > >> > >> Scim is dying and SCim2 is long away from usage. IBus was logical > choise. > >> so IBus-anthy was missing from SBo, so i added. it's easy for me to > >> maintain > >> a script when i use the program myself. > >> > > > > Yes, that why I wrote ibus and ibus-qt SlackBuild. ;-) Thanks for take > care > > of IBus-anthy. > > > >> > >> and i got used to my name not showing correctly now. UTF-8 would be nice > >> thou. > > > > Yes, I think UTF-8 is competent for international usage. But I'm sorry > that > > I don't know any technical details there... > > its implentation in gcc world is pretty bad. but most of the editor you can > use > supports unicode without any problem (like vim) and bash likes my full > unicode system. > however you may have problems with unicode scripts on non-unicode systems. > > is there way to point script encoding at the start (changing locale?) > That remind me of the way that Python handle this kind of problem: add a line "# -*- coding: -*-" at the header of the file. It's acceptable on my side. Anyway, waiting for advises from the admin team. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091206
2009/12/7 Ozan Türkyılmaz > > Scim is dying and SCim2 is long away from usage. IBus was logical choise. > so IBus-anthy was missing from SBo, so i added. it's easy for me to > maintain > a script when i use the program myself. > > Yes, that why I wrote ibus and ibus-qt SlackBuild. ;-) Thanks for take care of IBus-anthy. > and i got used to my name not showing correctly now. UTF-8 would be nice > thou. > Yes, I think UTF-8 is competent for international usage. But I'm sorry that I don't know any technical details there... -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091206
2009/12/7 Niklas 'Nille' Åkerström > > My name often gets unreadable, and i asked before about rules for text > encodings. > But there hasn't been any interest in unifying text encodings. > This goes for webbpage and slackbuilds since i don't like it when i can't > read my name in an .SlackBuild or .info when i click on them on SBo. > > I think this is a problem. AFAIK, French people have a website that is similar to SBo(maintain SlackBuilds that not in the stock tree). But they use French there, so no one else could understand what they are doing. SBo has big advantage over it: 1) competent admin team, in which someone is even in official slackware team.(afaik) 2) Using English as its "Official language". This point is not stated in any web page(or I missed them...). But everyone here speak English and everyone could understand it.(Someone may say "we also speak shell". ok ;-) However, it will be a problem if we *only* support English when facing the trend of internationalization. Name is one of it. If I put my real name in the script, I believe no one can see the correct characters unless '?' signs if we stick in English-only encodings. As a compromise and a gesture of integration, I use my "English name" here;-) But it will be wonderful to see colorful names in SlackBuild, web page, Changlog, etc. Just my 2 cents ;-) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20091206
On Mon, Dec 7, 2009 at 04:34, Robby Workman wrote: > Sun Dec 6 20:31:37 UTC 2009 > ... > misc/ibus-anthy: Added - an ibus module for Anthy Japanese conversion > engine. > Thanks to Ozan t?rky?lmaz. --rworkman Hrm, I see someone is interested in ibus now ;-) But the maintainer's name got garbled here... Should we unify the text encodings in the future? I think uft-8 is good. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Two problems writing SlackBuild for mendeley-desktop
On Tue, Dec 1, 2009 at 09:39, Alan Hicks wrote: > Apologies Grissiom, if you're on our mailing list and receive this > message twice. > > Actually I'm on the mailing list but doesn't receive it twice. Hmm, maybe GMail can remove duplicated mail automatically? > On Tue, 1 Dec 2009 09:27:27 +0800 > Grissiom wrote: > > > I'm writing a SlackBuild for Mendeley Desktop > > ( http://www.mendeley.com ), which is a research paper management > > tool. But I found two problems there. > > > > 1, It's a proprietary software, although you can use for free(free > > beer but not free speech) as long as you agree with it's 'terms and > > conditions'. Is it enough that I notice it in the README and let > > users be aware of it? > > That should be fine. Put it at the top of the README as it's own > sentence/paragraph all by itself so it stands out and I don't think > anyone will mind. The software may well be proprietary, but we're only > distributing build scripts, not the software or the source code, so > we're not really covered by whatever license that software is under. > > Yup, thanks for explanations. Then I know what should I do now. > > 2, It seems that the package have to make a /share directory. As it > > lays in the very root, I doubt whether it is something that a > > user-space package should do. I know I can link /share to /usr/share > > and pull things there. But we will have a /share eventually. > > Now that's ugly as sin in Sunday School. Are you absolutely certain > that things have to be placed in /share? I'm thinking that this > software may most properly be placed (nearly) completely under /opt > such as is done with openoffice.org. If it absolutely has to go > under /share, I guess that's something the admins will have to > consider. To the best of my knowledge, no software build script has > ever required the creation of a new top-level directory. > > Oops, sorry for disturbing. It's my fault. Everything would work fine when placed under /usr(including the share folder). So there is no problem now ;-) Thanks for your explanation. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Two problems writing SlackBuild for mendeley-desktop
Hello everyone, I'm writing a SlackBuild for Mendeley Desktop ( http://www.mendeley.com ), which is a research paper management tool. But I found two problems there. 1, It's a proprietary software, although you can use for free(free beer but not free speech) as long as you agree with it's 'terms and conditions'. Is it enough that I notice it in the README and let users be aware of it? 2, It seems that the package have to make a /share directory. As it lays in the very root, I doubt whether it is something that a user-space package should do. I know I can link /share to /usr/share and pull things there. But we will have a /share eventually. Thanks for the advises! -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] aria2 download link dead...
Hi, The link have changed and should be http://sourceforge.net/projects/aria2/files/stable/archives/aria2-1.6.0/aria2-1.6.0.tar.bz2now. The latest version is 1.6.3 now. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Please remove ibus-pinyin in the pending list
Hi, I am sorry that ibus-pinyin does not work well with gtk+2-2.14.7.(the setting dialog won't show up) This problem got fixed in upstream and I will re-submit the build scripts once the new version is released. Sorry for the unconvenience. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] opera/opera_chinese_font_fix.diff is not suitable for opera10
Hi all, I notice that the patch opera/opera_chinese_font_fix.diff is against usr/share/opera/ini/font.ini which is not in opera10. The counter file maybe usr/share/opera/defaults/font.ini. And the new ini file have already consider wqy-zenhei as good Chinese fonts. Maybe we only need to fix the Japanese fonts. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Why this archive got rejected?
On Sun, Sep 6, 2009 at 02:15, Heinz Wiesinger wrote: > On Saturday 05 September 2009 20:04:58 Grissiom wrote: >> Hi all, >> >> When I tried to submit this script archive(attachment), I got >> >> "There was something wrong with your .info file. It needs to be in the >> correct format. >> Please check the file and try again." >> >> Why? > > DOWNLOAD_x86_64 and MD5SUM_x86_64 are missing > Oh I got it~ Sorry ;( -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Why this archive got rejected?
Hi all, When I tried to submit this script archive(attachment), I got "There was something wrong with your .info file. It needs to be in the correct format. Please check the file and try again." Why? -- Cheers, Grissiom qt-doc.tar.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
On Mon, Aug 31, 2009 at 05:19, Heinz Wiesinger wrote: > On Sunday 30 August 2009 19:07:27 Robby Workman wrote: >> The binary-only is fine - I've been using it on x86_64 since >> well before any of you knew we had an x86_64 version :-) > > I agree. For most people the binary installer might be the best idea for now. > But, just to clarify, the once built slackware package of virtualbox-ose > hasn't any 32bit deps either. > Yes. Once you build a package, it hasn't any 32bit deps. But, does SBo provide any binary packages? NO. What if a user runs Slackware64 but doesn't have 32bit slackware in hand? I know you can always run the installer and let it pour files into /opt but we are talking about SlackBuilds which users can make use of the package system of Slackware, right? Is there any way to build package from the VBox installer? If so, it may become independent from the 32bit build environment. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unchecked entries for 13.0
Hmm, how could a system without rar support be useful? ;)
Also fix a bug in {C,CXX}FLAGS usage.
--
Cheers,
Grissiom
unrar.tar
Description: Unix tar archive
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unchecked entries for 13.0
For package I don't maintain: development/nose/, switch default ARCH from noarch to i486. misc/pinfo, add x86_64 SLKCFLAGS. I see development/pylint/ is still on the list so I made the tarball as well. -- Cheers, Grissiom pylint.tar Description: Unix tar archive nose.tar Description: Unix tar archive pinfo.tar Description: Unix tar archive ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unchecked entries for 13.0
multimedia/cuetools is ok on both 64bit and 32bit current. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unchecked entries for 13.0
On Thu, Aug 13, 2009 at 03:55, Keith Richie wrote:
>
> for qstardict try this
>
> qmake PLUGINS_DIR=/usr/lib${LIBDIRSUFFIX} QMAKE_CXXFLAGS="$SLKCFLAGS"
>
It works ;D
So here is the update.
Thanks a lot ;)
--
Cheers,
Grissiom
qstardict.tar
Description: Unix tar archive
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unchecked entries for 13.0
For development/pylint/, it's a pure python program which is compatible with python2.6. So it will be ok to push it to the 13.0 repo after switch the default ARCH tag to i486 or whatever not "noarch" since it use /usr/lib or /usr/lib64 depend on the system building it. For system/qstardict/, it's compatible with 32bit current but I failed to get qmake to install lib files into /usr/lib64, i.e., it will install something into /usr/lib even in 64bit system... If you think that's not a problem, you can push it into 13.0 repo. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Future Build Scripts
On Mon, Jun 29, 2009 at 16:10, Eric Hameleers wrote:
> On Sun, 28 Jun 2009, Darrell Anderson wrote:
>
> When 13.0 is released, will the slackbuilds.org build scripts continue
>> supporting the older tgz format, the newer txz format, or the option to use
>> either?
>>
>> Thanks.
>>
>> P.S. I'm not a member of the list.
>>
>> Darrell Anderson
>> http://humanreadable.nfshost.com/
>>
>
> It's really quite simple Darrell:
>
> We are a site that hosts SlackBuild scripts, not packages. It is not about
> supporting any particular package format. If you want to use the old .tgz
> packages, then by all means edit the last line of the script and change the
> extension of the package which is going to be created. These scripts are not
> set in concrete.
>
> When we start adding scripts for Slackware 13.0 in our repository, you can
> expect that they will (or should) support *all* of Slackware 13.0's features
> - which includes the new package formats. When we sign off a script after
> our internal QA round we will have tested it on a full install of Slackware.
>
> Regards, Eric
>
>
The problem becomes more clear when we know SBo only host scripts but not
packages and people can edit them when they feel disappointed. My suggestion
is add a FMT variable like this:
FMT=${FMT:-tgz}
...
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$FMT
So users don't need to modify the script to change the compression
algorithm.(As local modifications will lost after every rsync...)
--
Cheers,
Grissiom
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] mldonley.SlacBuild should be updated?
2009/6/5 Niklas 'Nille' Åkerström > Why don't you take over and maintain it since it's an orphaned slackbuild. > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2008-November/003181.html > So feel free to take over it and submit an update. > > Hmm, how did I miss that mail?... OK, I'll take is over and submit an update. Thanks. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20090605
On Fri, Jun 5, 2009 at 13:24, Robby Workman wrote: > Fri Jun 5 05:10:18 UTC 2009 > development/scons: Changed the default ARCH to i486 since the package > content > is arch-specific (with respect to file placement). --rworkman ... > libraries/mechanize: Changed the default ARCH to i486 since the package > content is arch-specific (with respect to file placement). --rworkman > ... > libraries/python-dateutil: Changed the default arch from noarch to i486. > So your admins reached a agreement? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] mldonley.SlacBuild should be updated?
On Fri, Jun 5, 2009 at 14:25, John Clizbe wrote: > > > I take a stab at it. It's blocking an upgrade of ocaml. > Anyway, you can pass --enable-force-ocaml to force usage of self-compiled Ocaml then every thing will go fine. Although it will take much more time... -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
2009/5/29 Dušan Stefanović > I'm not trying to hijack this thread, but there is another question > related to this discussion. What about i486 packages that are created > for slackware64? > slackware64 is multilib, so it is perfectly legal to do this. How > should I name package that has 32bit binary inside, but is created for > slack64? > > name-version-x86_64-build or name-version-i486-build or > name-version-i486-build_s64? > > Long time ago slack packages had different name scheme than today (you > can see it here: > ftp://ftp.slackware.no/pub/linux/slackware/slackware-4.0/slakware/d1/ > ). It was name.tgz, then after few releases it was changed to what we > know today name-version-arch-build. Pat already has problem with this > naming scheme, because it doesn't have slackware version (you can see > that at any slack mirror, just look at patches directory). I know that > it is for Pat to decide and not for as, but maybe it is time for > change. pkgtools are already changed for next release, so maybe it is > possible to add slackware version to naming scheme. > > regards, > ds > Yes, although the naming scheme is not the mission of this thread but I think it *may* provide a solution for this problem. Especially for the ones that think Slackware64 is just a other *version* of slackware but not the stoke slackware in x86_64 arch. But this will bring an other problem. What if the both the files *and* the directory structure are arch independent?(bash-completion as an example, although it not in slackware64 now) It's also non-sense to have two names with one package that exactly the same. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
On Fri, May 29, 2009 at 12:08, Chess Griffin wrote: > I am probably missing the finer points of this discussion, but it seems > to me that the current system works just fine. User A on a 32 bit > system who has not set ARCH as an environmental variable and builds a > package from a 'noarch' SlackBuild script, will end up with a package > with 'noarch' in the name and libraries in /usr/lib. That can be > re-distributed between other 32 bit systems. OTOH, User B on a 64 bit > sysem who has set ARCH as 'x86_64', either in the environment or > passing it to the SlackBuild script, will end up with a package with > 'x86_64' in the name, with libraries in /usr/lib64 which can be > redistributed between other 64 bit systems. > Yes, but currently some packages build from SlackBuilds(mostly for python modules) will install thing into /usr/lib64 even have "noarch" tag. > The truly independent 'noarch' packages are those simple ones that > simply build a single /usr/bin/ binary with make or that install icon > sets or something. > Hmm, I think rworkman will agree with you. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
On Fri, May 29, 2009 at 09:03, Robby Workman wrote: > Maybe, but I don't like the symlink idea at all. We can't just symlink > the entire /usr/lib (or /usr/lib64) directory, so we'd have to symlink > each additional file in there, and along the way, check for existing > files/dirs on the filesystem with the same names so that we don't wipe > them, and if they exist already, then what? Fail during installation? > > IMHO, if a package uses */lib64 then it's an ARCH=x86_64 package. > +1 for this ;) -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
On Fri, May 29, 2009 at 02:36, Eric Hameleers wrote: > > Hi Grissiom > > If you write a SlackBuild that installs purepython files which are > architecture independent you will indeed still have a "lib vs lib64" > difference in the final package depending on the architecture you > create the package on. > But since we are SlackBuilds.org and not LinuxPackages.net we do not > have to worry about where the final package gets built and installed - > the person who compiles it will know. > Hmm, Ok, so I know the role of SlackBuilds.org -- distribute the build script but not the packages and there is no guarantee that the packages build from the scripts are re-distributable? > > So, the purepython package can be "noarch" as long as you determine > the install-lib using Python itself: > > PYTHONLIB=$( python -c "from distutils.sysconfig import > get_python_lib; print get_python_lib()" ) > > This will yield "/usr/lib/python2.5/site-packages" on Slackware 12.2 > and "/usr/lib64/python2.6/site-packages" on slackware64-current. You > see that the python version number no longer needs to be hardcoded. > > Use that variable as follows: > > python setup.py install \ > --prefix=/usr \ > --install-lib=$PYTHONLIB \ > --root=$PKG > The setup.py will take care of this automaticially. Maybe there is no need to bother --install-lib if you do not want to re-distribute the package. You will not have to add the "if ARCH ... fi" block and the > LIBDIRSUFFIX is not used at all. A single SlackBuild will work on all > Slackware releases. Yes, SlackBuilds will always work. So the problem now is the package build from a SlackBuild is re-distributable or not or, do we want it to be re-distributable? -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
2009/5/28 Dušan Stefanović > On the other hand, why do you expect that package that is build on one > distribution work on another? > Do you expect that i486 package that is build for slack 12.2 work on 12.1? > Even vice versa is not true sometimes. I would never guess that > program will work just by looking at ARCH. > > regards, > ds > Hmm, I could not either ;) But I just want the packages live up to their names. -- Cheers, Grissiom ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
