VL 6.0 schedule

[uelsk8s]

Code:

If someone could walk me through for the first time, I would gladly make the Bibletime package for future versions.
Don't think I'll ever make a dev though.

no2

the first thing i do when i need to build a package is to type "packagename.slackbbuild" into google.
90% of the time i will find a slackbuild for the package. here is what i found for bibletime: http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-11.0/utilities/bibletime/1.6.4/src/bibletime.SlackBuild
downloading this and runnig it will make me a slackware tgz package, BUT running someone elses script without Knowing what it does is Dangerous, and it is not customized for VL.

to start with a script is just the linux commands used to make a package written together in a file. to make a package you need to 1)download the source tarball 2) extract it 3)configure the source 4)make the source 5)install the source into a temp package directory 6)put a description and any customizations into the temp pkg dir 7)run makepkg to compress the temp pkg dir into a package.
If you can put together the commands to do those 7 steps into a file you have a working buildscript. If i can type those commands and a have a working package why would i need a buildscript? well for 2 good reasons 1) the GPL says we have to have one and 2) if i have a good buildscript i will never have to type all those commands again the next tima a new VL version comes out.
So back to customizing the slackbuild i found. I will make comments inside the slackbuild below mine will start with 3 ###. the requirements comment says you will need sword and clucene-core so you will also have to find slackbuilds for those and maintain them. in the same dir that this script is ran you will also need the description file http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-11.0/utilities/bibletime/1.6.4/src/slack-desc
and the source and i18 tarballs
http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-11.0/utilities/bibletime/1.6.4/src/bibletime-1.6.4.tar.bz2
http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-11.0/utilities/bibletime/1.6.4/src/bibletime-i18n-1.6.4.tar.bz2

Code:

#!/bin/sh
# Heavily based on the Slackware 11.0 SlackBuild
# Requirements: sword, clucene-core
# http://www.bibletime.info
# Packager Vincenzi Loris - slacky@slacky.it
###modified for vectorlinux by Uelsk8s

CWD=`pwd`
TMP=${TMP:-/tmp/tgz}
PKG=$TMP/package-bibletime
NAME=bibletime
VERSION=1.6.4
###we dont use CHOST so i will comment it out and use CONFIGURE_TRIPLATE below instead so we can make 64bit packages from same script
#CHOST=i486
###VL packages are compiled with i586 as the ARCH we will make that dynamic here the script will run the command in the parentheses and return a value that we will use
ARCH=$(uname -m)
###the build should start with 1vl59 for VL5.9 and if we find a bug in the package we wil have to increase it to 2vl59
BUILD=1vl59
CONFIGURE_TRIPLATE=i486-slackware-linux

if [ "$ARCH" = "i?86" ]; then
  SLKCFLAGS="-O2 -march=i586 -mcpu=i686"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fpic"
 CONFIGURE_TRIPLATE=x86_64-pc-linux
fi

if [ ! -d $TMP ]; then
 mkdir -p $TMP
fi
if [ ! -d $PKG ]; then
 mkdir -p $PKG
fi

cd $TMP
tar xjvf $CWD/$NAME-$VERSION.tar.bz2
cd $NAME-$VERSION
chown -R root:root .
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure --prefix=/usr \
--program-prefix="" \
--program-suffix="" \
--build=$CONFIGURE_TRIPLATE
make -j4 || exit 1
make install DESTDIR=$PKG
mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a INSTALL LICENSE README $PKG/usr/doc/$NAME-$VERSION
tar xjvf $CWD/$NAME-i18n-$VERSION.tar.bz2
cd $NAME-i18n-$VERSION
chown -R root:root .
./configure --prefix=/usr \
--program-prefix="" \
--program-suffix="" \
$CONFIGURE_TRIPLATE
make -j4 || exit 1
make install DESTDIR=$PKG
cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/slack-desc > $PKG/usr/doc/$NAME-$VERSION/slack-desc
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild
### the requiredbuilder builder program needs to be installed or your package will not get dependancy info.
###(slapt-get --install requiredbuilder) should do it
requiredbuilder -v -y -s $CWD $PKG
makepkg -l y -c n $CWD/$NAME-$VERSION-$ARCH-$BUILD.tlz

if [ "$1" = "--cleanup" ]; then
 rm -rf $TMP
fi

If you have any questions after all that just ask.

Uelsk8s

[no2thesame]

I know this is opening up an old thread but I have, at long last, had the time and courage to package BibleTime. Thanks for the help Uelsk8s, I couldn't have done anything without it.
I have several questions.... but first the results. Here is my bibletime.SlackBuild :

Code:

!/bin/sh
# Heavily based on the Slackware 12.0 SlackBuild
# Requirements: sword, clucene-core
# http://www.bibletime.info
# Packager Vincenzi Loris - slacky@slacky.it
# modified for Vector Linux 5.9 by no2thesame

CWD=`pwd`
TMP=${TMP:-/tmp/tgz}
PKG=$TMP/package-bibletime
NAME=bibletime
VERSION=1.6.5
#CHOST=i486
ARCH=$(uname -m)
BUILD=1vl59
CONFIGURE_TRIPLATE=i486-slackware-linux

if [ "$ARCH" = "i?86" ]; then
  SLKCFLAGS="-O2 -march=i586 -mcpu=i686"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fpic"
 CONFIGURE_TRIPLATE=x86_64-pc-linux
fi

if [ ! -d $TMP ]; then
 mkdir -p $TMP
fi
if [ ! -d $PKG ]; then
 mkdir -p $PKG
fi

cd $TMP
tar xjvf $CWD/$NAME-$VERSION.tar.bz2
cd $NAME-$VERSION
find . \( -perm 777 -o -perm 775 -o -perm 711 \) -exec chmod 755 {} \;
find . \( -perm 700 -o -perm 555 -o -perm 511 \) -exec chmod 755 {} \;
find . \( -perm 666 -o -perm 664 -o -perm 600 \) -exec chmod 644 {} \;
find . \( -perm 444 -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
chown -R root:root .
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure --prefix=/usr \
--disable-debug \
--program-prefix= \
--program-suffix= \
--build=$CONFIGURE_TRIPLATE
#--build=$CHOST-slackware-linux
make -j4 || exit 1
make install DESTDIR=$PKG
mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a INSTALL LICENSE README $PKG/usr/doc/$NAME-$VERSION
tar xjvf $CWD/$NAME-i18n-$VERSION.tar.bz2
cd $NAME-i18n-$VERSION
find . \( -perm 777 -o -perm 775 -o -perm 711 \) -exec chmod 755 {} \;
find . \( -perm 700 -o -perm 555 -o -perm 511 \) -exec chmod 755 {} \;
find . \( -perm 666 -o -perm 664 -o -perm 600 \) -exec chmod 644 {} \;
find . \( -perm 444 -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \
chown -R root:root .
./configure --prefix=/usr \
--disable-debug \
--program-prefix= \
--program-suffix= \
--build=$CONFIGURE_TRIPLATE
#--build=$CHOST-slackware-linux
make -j4 || exit 1
make install DESTDIR=$PKG
cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/slack-desc > $PKG/usr/doc/$NAME-$VERSION/slack-desc
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild
requiredbuilder -v -y -s $CWD $PKG
makepkg -l y -c n $CWD/$NAME-$VERSION-$ARCH-$BUILD.tgz

if [ "$1" = "--cleanup" ]; then
 rm -rf $TMP
fi

A few issues:
the version is more recent than the one you demonstrated, have I altered the slackbuild correctly? I am not confident with my bash abilities.
 The resulting file is bibletime-1.6.5-i686-1vl59.tgz    is i686 correct?
 While it is building I get a lot of lines saying I don't have permission to chown. Should I be in root when I do this?
 
Installing and testing
I downloaded, modified the Slackbuild, packaged and installed clucene-core and sword as required, then installed BibleTime. It worked perfectly (amazingly!!). I like this version a lot.

I made a description-pak is this correct?:
 

Code:

pkg-name (bibletime-1.6.5-i686-1vl59.tgz)
Description: BibleTime
 BibleTime is a Bible study application for Linux. It is based on the
 K Desktop Environment and uses the Sword programming library to work
 with Bible texts, commentaries, dictionaries and books provided by
 the Crosswire Bible Society.
Required: sword, clucene-core
Website: http://www.bibletime.info
License: GNU GPL
Author: Joachim Ansorg, Martin Gruner, James Ots

Please correct anything you see here.
What is my next step?

no2

[caitlyn]

I'm not glad at all that the Mark All Upgrades and View Marked have been disabled. This is nannyism at its worst. I *like* to be able to see what upgrades are available in a way that's less laborious than going through the whole lengthy list of packages. Marking upgrades and viewing what's marked was a convenient way to do this. Even more convenient would be to list just the upgrades without marking them. Then have a View Available Upgrades option, leaving it to the user to mark the upgrades to install.

I'm not so foolish as to install all the upgrades. Usually, I don't install any of them. But I like to see what's available. I don't think every user should be deprived of a useful feature just because some people rush in where angels fear to tread. Why not a warning message--"DON'T upgrade a package just because an upgrade is available"--and a change in defaults so we can see just the upgrades if we so choose?

Jumping in late...  I am one of those people who DO upgrade most everything (not the kernel, obviously) and it has been perfectly safe to do so since 5.8 released and throughout the 5.8 and 5.9 lifecycle so far.  The reason most distros encourage this is that most updates to core packages should fall into one of two categories: 

1> Security patches
2> Bugfixes

Upgrading just because there is some cool new feature generally waits until the next release of the OS.  Although VL Has no hard and fast rule like this the fact is that we don't get a lot of upgrades and most do fit into those categories because that's what motivates people to build a new version of a core package.

So, I fundamentally agree with GrannyGeek.  In adidtion, disabling that feature was a really bad idea because it makes keeping a system secure difficult for a Linux newcomer.  It's something I actually criticize in my O'Reilly review of 5.9 (about to be posted). 

In future not only would I like to see that functionality restored but I'd like to see gslapt-notifier integrated into the default Xfce desktop.

[kc1di]

Wow, I'm gone a week and miss a lot!

If someone could walk me through for the first time, I would gladly make the Bibletime package for future versions.
Don't think I'll ever make a dev though.

no2

Hi no2,

I think your on the  right track , and know you'll get the help you need,  I've already packaged bibletime 1.6.5 and it's dependancies .. but it has not been moved to the repository as yet you can see my post at http://www.vectorlinux.com/forum2/index.php?topic=5861.0

Cheers !
Dave

[no2thesame]

Hi no2,

I think your on the  right track , and know you'll get the help you need,  I've already packaged bibletime 1.6.5 and it's dependancies .. but it has not been moved to the repository as yet you can see my post at http://www.vectorlinux.com/forum2/index.php?topic=5861.0

Cheers !
Dave

Hello Dave,
after sweating blood (figuratively... but appropriate this time of year) to do my first package, I'm miffed that you beat me to it. But I'm glad that someone has finally done it.

And Gslapt almost fooled me into believing it was on the repository just now, until I checked on another machine. Then I noticed the location is my home directory.

I couldn't follow the link to your post either. ?permissions?

I have a question now (at risk of diverting this thread)... where can I see the buildscript and description-pak of a package in the VL repository? Just so I know how they 'should' look.

Thanks,
no2

[kc1di]

Hi no2,

I think your on the  right track , and know you'll get the help you need,  I've already packaged bibletime 1.6.5 and it's dependancies .. but it has not been moved to the repository as yet you can see my post at http://www.vectorlinux.com/forum2/index.php?topic=5861.0

Cheers !
Dave

Hello Dave,
after sweating blood (figuratively... but appropriate this time of year) to do my first package, I'm miffed that you beat me to it. But I'm glad that someone has finally done it.

And Gslapt almost fooled me into believing it was on the repository just now, until I checked on another machine. Then I noticed the location is my home directory.

I couldn't follow the link to your post either. ?permissions?

I have a question now (at risk of diverting this thread)... where can I see the buildscript and description-pak of a package in the VL repository? Just so I know how they 'should' look.   

Thanks,
no2

Hi again no2,

Well I didn't run into your thread until this afternoon I had packaged it last week because I wanted it on one of my machines.. I also use E-sword with wine both are good Bible Study programs. 

If I can be of help to you in the future in packaging any programs let me know. As we need as many packagers as we can get..  right now the bottleneck seems to be getting them moved over into the repositories as there are only a few members that can do that.   I forgot the link I sent you is not open to the public. 
any way don't give up and Lord Bless. And now we better turn the thread back to it's original intent.

Dave


Here is the Build Script that I used to build it..

Code:

#!/usr/bin/bash
# This script assumes it will be launched within "/NAME/VERSION/src" dir.
# With all sources in "src" Your Vector Linux .tlz package, slack-desc,
# and slack-required will be found in "VERSION" dir. The extraction and
# build will be in a temp dir created in "NAME" dir, and then removed on exit.
# Comment out second to last line to keep this dir intact.


NAME="bibletime"            #Enter package Name!
VERSION=${VERSION:-"1.6.5"}      #Enter package Version!
VL_PACKAGER=${VL_PACKAGER:-"KC1DI"}   #Enter your Name!


#SYSTEM VARIABLES
#----------------------------------------------------------------------------
BUILDNUM=${BUILDNUM:-"1"}
VL_VERSION=${VL_VERSION:-"$(ls /var/log/packages/|grep vlconfig2|cut -d "-" -f4|cut -c 2-5)"}
BUILD=${BUILD:-"$BUILDNUM""$VL_VERSION"}
ARCH=${ARCH:-$(uname -m)}
CONFIG_OPTIONS=${CONFIG_OPTIONS:-""}
LDFLAG_OPTIONS=${LDFLAG_OPTIONS:-""}
#----------------------------------------------------------------------------


#SETUP PACKAGING ENVIRONMENT
#--------------------------------------------
CWD=$(pwd)
cd ../
RELEASEDIR=$(pwd)
cd $CWD
mkdir -p $RELEASEDIR/tmp
TMP=$RELEASEDIR/tmp
PKG=$TMP/package-$NAME
#--------------------------------------------


if [ $UID != 0 ]; then
   echo "You are not authorized to run this script. Please login as root"
   exit 1
fi

if [ ! -x /usr/bin/requiredbuilder ]; then
   echo "Requiredbuilder not installed, or not executable."
   exit 1
fi

if [ $VL_PACKAGER = "YOURNAME" ]; then
   echo 'Who are you?
   Please edit VL_PACKAGER=${VL_PACKAGER:-YOURNAME} in this script.
   Change the word "YOURNAME" to your VectorLinux packager name.
   You may also export VL_PACKAGER, or call this script with
   VL_PACKAGER="YOUR NAME HERE"'
   exit 1
fi


#CFLAGS SETUP
#--------------------------------------------
if [[ "$ARCH" = i?86 ]]; then
  ARCH=i586
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  CONFIGURE_TRIPLET="i486-slackware-linux"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fpic"
  CONFIGURE_TRIPLET="x86_64-pc-linux"
fi

export CFLAGS="$SLKCFLAGS $CFLAG_OPTIONS"
export CXXFLAGS=$CFLAGS
export LDFLAGS="$LDFLAGS $LDFLAG_OPTIONS"
#--------------------------------------------


rm -rf $PKG
mkdir -p $PKG
cd $TMP
rm -rf $NAME-$VERSION


#EXTRACT SOURCES
#-----------------------------------------------------
echo "Extracting source..."
tar xvf $CWD/$NAME-$VERSION.tar.* || exit 1
#-----------------------------------------------------


cd $TMP/$NAME-$VERSION


#SET PERMISSIONS
#-----------------------------------------
echo "Setting permissions..."
chown -R root:root .
find . -perm 664 -exec chmod 644 {} \;
find . -perm 777 -exec chmod 755 {} \;
find . -perm 2777 -exec chmod 755 {} \;
find . -perm 775 -exec chmod 755 {} \;
find . -perm 2755 -exec chmod 755 {} \;
find . -perm 774 -exec chmod 644 {} \;
find . -perm 666 -exec chmod 644 {} \;
find . -perm 600 -exec chmod 644 {} \;
find . -perm 444 -exec chmod 644 {} \;
find . -perm 400 -exec chmod 644 {} \;
find . -perm 440 -exec chmod 644 {} \;
find . -perm 511 -exec chmod 755 {} \;
find . -perm 711 -exec chmod 755 {} \;
find . -perm 555 -exec chmod 755 {} \;
#-----------------------------------------


#CONFIGURE & MAKE
#----------------------------------------------------------------------
# If you are building a KDE-related app, then change the following
# arguments in the script below:
# --prefix=$(kde-config -prefix) \
# --sysconfdir=/etc/kde \
#
# Making these changes will ensure that your package will build in the
# correct path and that it will work seamlessly within the KDE environment.
#
#-----------------------------------------------------------------------
echo "Configuring source..."
./configure --prefix=/usr \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  --with-included-gettext \
  --disable-debug \
  --program-prefix="" \
  --program-suffix="" \
  --build=$CONFIGURE_TRIPLET \
  $CONFIG_OPTIONS || exit 1

make || exit 1

make install DESTDIR=$PKG || exit

#######################################################################
#Miscellenious tweaks and things outside a normal ./configure go here #
#######################################################################

#mkdir -p $PKG/usr/share/applications
#cp $CWD/$NAME.desktop $PKG/usr/share/applications/$NAME.desktop
#mkdir -p $PKG/usr/share/pixmaps
#cp $CWD/$NAME.png $PKG/usr/share/pixmaps/$NAME.png

mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a AUTHORS COPYING ChangeLog Credits MANIFEST README TODO \
   $PKG/usr/doc/$NAME-$VERSION
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild

#----------------------------------------------------------------------

if [ -d $PKG/usr/share/man ] ; then
  mkdir -p $PKG/usr/man
  mv $PKG/usr/share/man/* $PKG/usr/man
  rm  $PKG/usr/share/man
fi
find $PKG/usr/man -type f -exec gzip -9 {} \;

if [ -d $PKG/usr/share/info ] ; then
  mkdir -p $PKG/usr/info
  mv $PKG/usr/share/info/* $PKG/usr/info
  rm $PKG/usr/share/info
fi 
find $PKG/usr/info -type f -exec gzip -9 {} \;

mkdir -p $PKG/install

           # This creates the white space in front of "handy-ruler" in slack-desc below.

      LENGTH=$(expr length "$NAME")
      SPACES=0
      SHIM=""
      until [ "$SPACES" = "$LENGTH" ]; do
        SHIM="$SHIM "
        let SPACES=$SPACES+1
      done

# Fill in the package summary between the () below.
# Then package the description, License, Author and Website.
# There may be no more then 11 $NAME: lines in a valid slack-desc.

cat > $RELEASEDIR/slack-desc << EOF
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.  Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in.  You must
# make exactly 11 lines for the formatting to be correct.  It's also
# customary to leave one space after the ':'.
   
$SHIM|-----handy-ruler------------------------------------------------------|
$NAME: $NAME (bibletime)
$NAME: BibleTime is a Bible study application for Linux.
$NAME: It is based on the K Desktop Environment and uses the Sword
$NAME: programming library to work with Bible texts, commentaries,
$NAME: dictionaries and books provided by the Crosswire Bible Society.
$NAME:
$NAME:
$NAME: License: GPL
$NAME: Authors:
$NAME: Website: http://www.bibletime.info/software_about.html


#----------------------------------------
BUILDDATE: $(date)
PACKAGER:  $VL_PACKAGER
HOST:      $(uname -srm)
DISTRO:    $(cat /etc/vector-version)
CFLAGS:    $CFLAGS
LDFLAGS:   $LDFLAGS
CONFIGURE: $(awk "/\.\/configure\ /" $TMP/$NAME-$VERSION/config.log)

EOF

cat $RELEASEDIR/slack-desc > $PKG/install/slack-desc


#STRIPPING
#------------------------------------------------------------------------------------------------------------------
cd $PKG
echo " "
echo "Stripping...."
echo " "
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
#------------------------------------------------------------------------------------------------------------------


#FINISH PACKAGE
#--------------------------------------------------------------
echo "Finding dependencies..."
requiredbuilder -v -y -s $RELEASEDIR $PKG
echo "Creating package $NAME-$VERSION-$ARCH-$BUILD.tlz"
makepkg -l y -c n $RELEASEDIR/$NAME-$VERSION-$ARCH-$BUILD.tlz

cd $CWD
echo "Cleaning up temp files..." && rm -rf $TMP
echo "Package Complete"
#--------------------------------------------------------------

also here is the slack-desc and slack-required files.

Code:

# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.  Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in.  You must
# make exactly 11 lines for the formatting to be correct.  It's also
# customary to leave one space after the ':'.
   
         |-----handy-ruler------------------------------------------------------|
bibletime: bibletime (bibletime)
bibletime: BibleTime is a Bible study application for Linux.
bibletime: It is based on the K Desktop Environment and uses the Sword
bibletime: programming library to work with Bible texts, commentaries,
bibletime: dictionaries and books provided by the Crosswire Bible Society.
bibletime:
bibletime:
bibletime: License: GPL
bibletime: Authors: Joachim Ansorg, Martin Gruner, James Ots
bibletime: Website: http://www.bibletime.info/software_about.html


#----------------------------------------
BUILDDATE: Sun Mar 16 21:22:28 UTC 2008
PACKAGER:  KC1DI
HOST:      Linux 2.6.22.14 i686
DISTRO:    5.9 SOHO Alpha3.4 built on Mar-08-08
CFLAGS:    -O2 -march=i586 -mtune=i686
LDFLAGS:   
CONFIGURE:   $ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/man --with-included-gettext --disable-debug --program-prefix= --program-suffix= --build=i486-slackware-linux

Code:

acl >= 2.2.39_1-i486-2
attr >= 2.4.32_1-i486-2
clucene-core >= 0.9.20-i586-1vl59
curl >= 7.17.0-i586-1vl59
cxxlibs >= 6.0.8-i486-4 | gcc-g++ >= 4.1.2-i486-1
cyrus-sasl >= 2.1.22-i486-1
expat >= 2.0.1-i486-1
fbopenssl >= 0.0.4-i586-1vl59
fontconfig >= 2.4.2-i486-2
freetype >= 2.3.5-i486-1
gamin >= 0.1.8-i486-2
gcc >= 4.1.2-i486-1
glibc-solibs >= 2.5-i486-5
kdelibs >= 3.5.9-i586-2vl59
lcms >= 1.16-i486-1
libICE >= 1.0.4-i486-1
libSM >= 1.0.3-i486-1
libX11 >= 1.1.3-i486-1
libXau >= 1.0.3-i486-1
libXcursor >= 1.1.9-i486-1
libXdamage >= 1.1.1-i486-1
libXdmcp >= 1.0.2-i486-1
libXext >= 1.0.3-i486-1
libXfixes >= 4.0.3-i486-1
libXft >= 2.1.12-i486-2
libXi >= 1.1.3-i486-1
libXinerama >= 1.0.2-i486-1
libXmu >= 1.0.3-i486-1
libXrandr >= 1.2.2-i486-1
libXrender >= 0.9.4-i486-1
libXt >= 1.0.5-i486-1
libXxf86vm >= 1.0.1-i486-1
libart_lgpl >= 2.3.19-i486-1
libdrm >= 2.3.0-i486-1
libidn >= 0.6.10-i486-1
libjpeg >= 6b-i486-5
libmng >= 1.0.9-i486-1
libpng >= 1.2.25-i586-2vl59
libssh2 >= 0.17-i586-1vl59
libxcb >= 1.0-i486-2
mesa >= 7.0.2-i486-1
openldap-client >= 2.3.32-i486-1
openssl >= 0.9.8f-i486-1 | openssl-solibs >= 0.9.8f-i486-1
pcre >= 7.3-i486-1
qt >= 3.3.8b-i586-3vl59
sword >= 1.5.10-i586-1vl59
zlib >= 1.2.3-i486-2

[no2thesame]

Hi again no2,

Well I didn't run into your thread until this afternoon I had packaged it last week because I wanted it on one of my machines.. I also use E-sword with wine both are good Bible Study programs. 

If I can be of help to you in the future in packaging any programs let me know. As we need as many packagers as we can get..  right now the bottleneck seems to be getting them moved over into the repositories as there are only a few members that can do that.   I forgot the link I sent you is not open to the public. 
any way don't give up and Lord Bless. And now we better turn the thread back to it's original intent.

Dave

Thanks for all the info Dave, it's good to see how people approach the problem.

Hey, don't feel bad that you beat me, I took ages to get around to the job and I've learnt heaps so far. Looking forward to examining your files. I might take you up on that help in future too.

eSword is sweet, pity it isn't open source. But I like the new BibleTime too.

no2

[Windozer]

[...] that the Mark All Upgrades and View Marked have been disabled. [...] I *like* to be able to see what upgrades are available in a way that's less laborious than going through the whole lengthy list of packages. [...]

[...] In future not only would I like to see that functionality restored but I'd like to see gslapt-notifier integrated [...]

Hope you all don't mind that I pull this older thread back on top of the heap, but this is enough to make me consider not upgrading from 5.8 to 5.9 --- I prefer to do the same method as G.G.

Did this get resolved since then, in a sub-release of 5.9, or is it slated for 6.0?

thanks,
Howard in Florida
~~~~~~~~~~

[GrannyGeek]

Hope you all don't mind that I pull this older thread back on top of the heap, but this is enough to make me consider not upgrading from 5.8 to 5.9 --- I prefer to do the same method as G.G.

Did this get resolved since then, in a sub-release of 5.9, or is it slated for 6.0?

I'm happy to say it's back in VL6. I haven't checked in VL6 beta 2 yet, but it's been in previous test versions.

VL 6 is really nice and has been quite stable throughout the public alpha cycle and now the betas. Do plan to upgrade to it when the final version comes out (should be very soon).
--GrannyGeek

[Windozer]

[...] VL 6 is really nice [...] --GrannyGeek

Thanks, GrannyGeek.

cool!  Maybe I'll try out the beta, and do a bit of testing.

cheers,
Howard

[caitlyn]

Release Candidate 1 is even nicer than the betas   The big addition, IMHO, is gslapt-notifier, a little daemon that pops a red icon up on your panel when patches are available.  One click and they can be installed.  This makes keeping a VL system patched and secure as easy as Ubuntu or Fedora or any other distro you care to name.

Thanks to some help from two VL develpers (Uelsk8s and Vector) I've got it running very nicely on my Sylvania g netbook.  I did have to upgrade to a 2.6.27.10 kernel and update mesa and libdrm to get the Via Chrome graphics chipset working correctly and to get support for my built-in webcam.  Once that was done, though... 

I still have a couple of minor issues to work out and I already know what the likely fixes are. 

Anyway, IMHO VL6 is really looking like it will be a sweet release, as in the best from Vector Linux to date.

[Windozer]

Release Candidate 1 is even nicer than the betas   [...] Anyway, IMHO VL6 is really looking like it will be a sweet release, as in the best from Vector Linux to date.

COOL!

Caitlyn, I just DL'ed it a few minutes ago. Will try it out on a duel proc with a sata drive that has a ton of partitions, including Bill's favorite money machine  <G>

Do you think you'll find time to do a write up on it? Your review of an earlier release led me to making the post above.  I found that review to be very thorough and clear. As a former tech-writer and translator, I appreciate that level of detail all the more.

Have a feeling I'll be seconding your vote for V6 here soon 


cheers,
- Howard in FL
~~~~~~~~~

[caitlyn]

Hi, Howard,

I did the review of Beta 2 for DistroWatch Weekly at the request of DW owner/editor Ladislav Bodnar.  That writing gig was actually paid.  When I'm paid to write I always try to do what my editor wants  

In general I don't review betas or release candidates.  I review final releases only after I have time to really work with them.  I do expect to review Vector Linux 6 for the O'Reilly Broadcast website.  Hopefully the editor of linux.oreilly.com will also choose it for inclusion and various Linux portal sites will pick it up.  That won't happen for a while yet, though.

Thanks for your nice compliment, BTW.  It is appreciated.

Regards,
Cait

[Dweeberkitty]

Anyway, IMHO VL6 is really looking like it will be a sweet release, as in the best from Vector Linux to date.

Hehe, seems like that's the case with almost every release. It just keeps getting better....