Skip to content
Commits on Feb 4, 2015
Commits on Apr 2, 2013
  1. Fix some more compiler warnings

    committed Apr 1, 2013
  2. Build system fixes

    committed Apr 1, 2013
  3. Fix compiler warnings

    committed Apr 1, 2013
  4. Update autotools configuration

    committed Dec 24, 2011
  5. Fix package database format to better match original pkgtools

    committed Dec 23, 2011
    As per report by Ruarí Ødegaard:
    
    The formatting of /var/log/packages/* files that spkg creates differ from
    the official Slackware Pkgtools. Hence when used on a system like Salix
    any scripts that assume Slackware formatting may fail.
    
    The two obvious most obvious differences are that "PACKAGE SIZE"
    information is not the same format as installpkg would use. Also the
    contents of install/ are intentionally left out meaning you can't use this
    information to check if a package doinst.sh, without also looking at
    /var/log/scripts. There are also some differences in tabbing/spacing.
    
    With regards to the "PACKAGE SIZE" information, the official pkgtools
    switch from bytes, to kilobytes, to megabytes (and perhaps one day
    gigabytes if we ever get packages that big) as each size boundary is hit.
    spkg uses bytes and kilobytes only and even for then formats the packages
    bigger than a kilobyte differently to Slackware (by adding a space after
    file size and before the K). For example, after Opera is installed with
    spkg:
    
    $ head -n 4 /var/log/packages/opera-11.60-i686-1ro
    PACKAGE NAME:              opera-11.60-i686-1ro
    COMPRESSED PACKAGE SIZE:   11239 K
    UNCOMPRESSED PACKAGE SIZE: 36608 K
    PACKAGE LOCATION:          opera-11.60-i686-1ro.txz
    
    After Opera is installed with the installpkg:
    
    $ head -n 4 /var/log/packages/opera-11.60-i686-1ro
    PACKAGE NAME:     opera-11.60-i686-1ro
    COMPRESSED PACKAGE SIZE:     11M
    UNCOMPRESSED PACKAGE SIZE:     36M
    PACKAGE LOCATION: opera-11.60-i686-1ro.txz
Commits on Aug 29, 2012
  1. @Yousha

    Updated.

    Yousha committed Aug 29, 2012
Commits on Aug 25, 2012
  1. Merge pull request #3 from Yousha/master

    committed Aug 25, 2012
    README file updated #2.
Commits on Mar 16, 2011
  1. Prepare version 1.0 release

    committed Mar 16, 2011
  2. Automatically run gtk-update-icon-cache if necessary (patch by George…

    committed Mar 16, 2011
    … Vlahavas)
    
    Signed-off-by: Ondrej Jirman <megous@megous.com>
Commits on Jun 27, 2010
  1. Updated website

    committed Jun 27, 2010
Commits on Jun 14, 2010
  1. Bump version to 1.0rc13

    committed Jun 14, 2010
  2. Implemented force install

    committed Jun 14, 2010
    This option when used will create problems with package ambiguity during
    upgrade. spkg will pick random package with given shortname for upgrade.
    
    Make sure you know what you are doing, if you choose to use this option.
Commits on Apr 12, 2010
  1. bump version to 1.0rc12

    committed Apr 12, 2010
  2. increase some limits

    committed Apr 12, 2010
Commits on Jun 12, 2009
Commits on Jun 9, 2009
  1. Fix xzdec options

    committed Jun 9, 2009
  2. Updated download docs

    committed Jun 9, 2009
  3. Fixed static spkg build

    committed Jun 9, 2009
Commits on May 25, 2009
  1. Bump version to 1.0rc10

    committed May 25, 2009
  2. Windows support from Laura Michaels at <ml@distasis.com>

    committed May 25, 2009
    I put together the equivalent of a SlackBuild script for building spkg on
    Windows with msys.  Am hoping it will work on the Linux side as well (for
    cross-compiling with mingw) without too many changes needed.  You may have to
    fix things like directory locations.
    
    I downloaded popt-1.8.1 from the gnuwin32 project at sourceforge.  I also
    downloaded and compiled judy-1.0.4 from the link at your site.  The glib library
    was probably from the GTK site.  They supplies GTK libraries for Win32.  Some of
    the functions available on Linux/posix machines aren't built-in for Win32.
    Specifically, fnmatch, flock, getline, utime and link were missing.  There are
    several Open Source projects that already supplied routines for some of these,
    so rather than reinventing the wheel, I borrowed code from them.  Links to the
    source are in the spkg.sh script.  I did notice other libraries besides the ones
    I used that also supplied these functions and they could be used pretty much
    interchangeably or the routines could probably be rewritten if you want original
    source for them.  For utime and link functions, I examined some Open Source code
    that implemented them, checked the Linux man pages and Windows documentation on
    the related functions and wrote them.  You're welcome to put whatever kind of
    licensing would work best with spkg for those two files/routines.  The various
    Win32 patches are in the spkg.patch file and part of the spkg.sh build script.
    I #ifdef'd Windows changes as __WIN32__ so all previous code should still
    compile fine on other systems.  The spkg.sh script assumes you have makepkg on
    your system to package the final program.  Probably not a problem on Linux, but
    I did do some porting of the makepkg script to get it working with msys since it
    isn't readily available on Windows.
    
    The program seems to build fine on my Windows XP machine using mingw and msys.
    I tried installing, updating, listing and removing a couple of packages.
    Eventually, would like to add some kind of support for slack-required files, but
    haven't had any time to look into that further.  I've been running the program
    from within msys.  That's probably where I'd use it anyway, when building
    libraries for mingw within the msys environment.  Haven't tried running it
    straight from a command prompt, but don't see any reason why it shouldn't work
    that way as well.
    
    I think spkg makes a great tool for developers for keeping track of all those
    Open Source libraries that end up on a system.  Am hoping to rebuild some of the
    libraries and programs I've been working with, using something similar to
    slackbuild scripts to keep track of all the steps and any necessary patches.
    Then I can use spkg to install and keep track of what's on my system.  Thanks so
    much for sharing the code for this tool.  A C implementation is so much nicer
    than a bunch of shell script files.
    
    Hope you can make use of the mingw additions.  If you have any questions about
    what I did to get it to build on Windows, please let me know.
    
    Signed-off-by: Ondrej Jirman <megous@megous.com>
Commits on Jan 27, 2007
  1. update news file

    committed Jan 27, 2007
  2. cleanup signal handling

    committed Jan 27, 2007
  3. bump version to 1.0rc9

    committed Jan 27, 2007
Commits on Nov 4, 2006
Something went wrong with that request. Please try again.