DeLi(cate) Forum
PKGBUILD files - Printable Version

+- DeLi(cate) Forum (http://delicate-linux.net/forum)
+-- Forum: DeLi(cate) Linux [english only] (/forumdisplay.php?fid=3)
+--- Forum: Development (/forumdisplay.php?fid=6)
+--- Thread: PKGBUILD files (/showthread.php?tid=74)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33


RE: PKGBUILD files - tavvva - 01-10-2012 09:24 PM

(01-10-2012 03:59 PM)Compact Wrote:  Menu-header
Office
Tools
Network
Graphics
AudioVideo
Console-game
Game
Settings
Menu-footer-shutdown

Yes ... these are supported at the moment ...


RE: PKGBUILD files - nl2stk - 01-11-2012 01:52 PM

(01-11-2012 12:34 PM)Compact Wrote:  And is there a copy and pastable md5 generator for Delicate under X ?

I could tell you how I do it.
After downloading the original source package, I take the sum in the terminal with 'md5sum example.tar.gz'. After that I select the sum with the left mousebutton, after that I click on it with the middle button (in my case the scrollwheel). If everything goes well, you 'll see the sum on the prompt When your making a PKGBUILD in leafpad and you need that sum, all you have to do is just click with the middle button, and voila it's pasted.

I'll hope it's understandable English, I'm on medication and it's not what it suppose to be Confused


RE: PKGBUILD files - tavvva - 01-11-2012 03:37 PM

(01-11-2012 12:34 PM)Compact Wrote:  Links 2.5

Links 2.2 is already in our repo :] Currently maintained by me :]

http://delicate.tavvva.net/0.1/src/links/2.2-3/

But if You feel You would like to be the maintainer ... it's all Yours :]

Btw .... the following wouldn't work:
Icon=links_32x32.xpm

The right suffix and size has to be chosen by the menu-generator since the pixmap support in the particular WMs doesn't work like we want (=sucks). Please, do not force exact icon resolutions and formats. These will be chosen by the menu generator and possibly automatically changed to a better format in the future .... this can be easily automated if there's no size and suffix. This entry is useful only in cases, where there are 2 or more .desktop files using different icons inside the same package. That's why it is still there even if it contains mostly the same content like the Name= or Exec= entries ...


RE: PKGBUILD files - tavvva - 01-11-2012 04:18 PM

(01-11-2012 01:52 PM)nl2stk Wrote:  
(01-11-2012 12:34 PM)Compact Wrote:  And is there a copy and pastable md5 generator for Delicate under X ?
I could tell you how I do it.
After downloading the original source package, I take the sum in the terminal with 'md5sum example.tar.gz'. After that I select the sum with the left mousebutton, .....

Guyyyyyys Big Grin Big Grin

makepkg -g
-OR-
makepkg -g >> PKGBUILD

Have You noticed, that many of my PKGBUILDs have the md5sums at the bottom? :]
I've already mentioned that somewhere in this forum, but ok .... it's lost in the heap of comments and You probably couldn't read them all ...

!!!WARNING!!!:
1.) be very careful when using the second variant .... if You type just one > sign, then Your PKGBUILD is lost !
2.) use it only when all the sources are already downloaded, otherwise You would generate a junk into Your PKGBUILD


RE: PKGBUILD files - nl2stk - 01-11-2012 11:24 PM

(01-11-2012 04:18 PM)tavvva Wrote:  Guyyyyyys Big Grin Big Grin

makepkg -g
-OR-
makepkg -g >> PKGBUILD

Hehehe and I thought copy and paste from the terminal to (x application) was easy enough Tongue
Well perhaps for other stuff...


RE: PKGBUILD files - snacsnoc - 01-13-2012 10:48 PM

Nginx

PKGBUILD:
Code:
pkgname=nginx
pkgver=1.0.11
pkgrel=$(date -u +%Y%m%d%H)
pkgdesc="A high-performance HTTP server, reverse proxy and IMAP/POP3 proxy server"
arch=(i386)
url="http://nginx.org/"
license=(custom)
depends=(zlib openssl)
source=(
  nginx.rc
  http://nginx.org/download/$pkgname-$pkgver.tar.gz
)


install=$pkgname.install


build(){
cd "$srcdir/$pkgname-$pkgver"
  ./configure \
    --prefix=/usr \
    --conf-path=/etc/nginx/nginx.conf \
    --sbin-path=/usr/sbin/nginx \
    --with-mail  --with-http_ssl_module \
    --with-http_gzip_static_module \
    --group=www \
    --with-ipv6

    make || return 1
    make DESTDIR=$pkgdir install


    install -D -m755 $srcdir/nginx.rc $pkgdir/etc/rc.d/nginx
    install -D LICENSE $pkgdir/usr/share/licenses/nginx/LICENSE
}
check() {
    cd "$srcdir/$pkgname-$pkgver"
    make -k check
}
package() {
    cd "$srcdir/$pkgname-$pkgver"
    make DESTDIR=$pkgdir install
}
md5sums=('c37a033828a26699f29a0f648e4496b3' 'a41a01d7cd46e13ea926d7c9ca283a95')
md5sums=('72671a18901eae6a0d312b3d0730bb91' 'a41a01d7cd46e13ea926d7c9ca283a95')
nginx.rc:
Code:
#!/bin/sh
# http://wiki.nginx.org/Standalone_daemon

NGINX_BASE_DIR="/usr"
NGINX_DAEMON="${NGINX_BASE_DIR}/sbin/nginx"
NGINX_CONF="/etc/nginx/nginx.conf"

__launch_signal( ) {

  ${NGINX_DAEMON} -s ${1} &>/dev/null
}

__checkconfig( ) {

  ${NGINX_DAEMON} -c ${NGINX_CONF} -t &>/dev/null
}

__start( ) {

  [ -r ${NGINX_CONF} ] || exit 1

  __checkconfig && ${NGINX_DAEMON} -c ${NGINX_CONF} &>/dev/null || return ${?}
}

__stop( ) {

  __launch_signal stop
}

__reload( ) {

  __checkconfig && __launch_signar reload || return ${?}  
}

__restart( ) {

  __stop && __start
}

__show_usage( ) {

  echo "Usage: ${0} {start|stop|restart|reload}"
  exit 3
}

##
# :: main ::
case "${1}" in
  start|stop|restart|reload)
    [ -x ${NGINX_DAEMON} ] || exit 2
    __${1}
    ;;
  *)
    __show_usage
    ;;
esac
[/quote]
And nginx.install:
Code:
op=$1
shift
$op $*



RE: PKGBUILD files - nl2stk - 01-14-2012 01:16 AM

@snacsnoc.
Welcome here!

I saw your PKGBUILD and I would like to make a few comments Smile
The PKGBUILD from Delicate is slightly different than you perhaps know from Arch (?).
An example:

(01-13-2012 10:48 PM)snacsnoc Wrote:  arch=(i386)

The 'arch' statement is not included in the PKGBUILD for Delicate (AFAIK).
To make a '386' compatible package, it works a bit different..
I higly recommend this topic: http://delicate.tavvva.net/forum/showthread.php?tid=160&pid=795#pid795
It explains the most common things, and contains a lot of my corrected mistakes.
Some things might be obvious and other things are Delicate specific, perhaps it's usefull .


RE: PKGBUILD files - tavvva - 01-14-2012 04:51 PM

Hello guys.

From NOW (till the end of the universe) there's no need for the menu-generator-trigger calls in the .install files. If Your .install file contains just the trigger and nothing else, then throw it away completely...


RE: PKGBUILD files - snacsnoc - 01-15-2012 02:41 AM

(01-14-2012 01:16 AM)nl2stk Wrote:  @snacsnoc.
Welcome here!

I saw your PKGBUILD and I would like to make a few comments Smile
The PKGBUILD from Delicate is slightly different than you perhaps know from Arch (?).
An example:

(01-13-2012 10:48 PM)snacsnoc Wrote:  arch=(i386)

The 'arch' statement is not included in the PKGBUILD for Delicate (AFAIK).
To make a '386' compatible package, it works a bit different..
I higly recommend this topic: http://delicate.tavvva.net/forum/showthread.php?tid=160&pid=795#pid795
It explains the most common things, and contains a lot of my corrected mistakes.
Some things might be obvious and other things are Delicate specific, perhaps it's usefull .
Thanks! It would be nice if there a nice straightforward guide (perhaps a skeleton package) for Delicate packages, as now I know it's different from building an Arch package. I'll check it out that topic out.


RE: PKGBUILD files - tavvva - 01-15-2012 11:29 AM

(01-11-2012 07:59 PM)Compact Wrote:  find $pkgdir -name '*.pod' -delete

This form is much better .... we'll use it for the libtool stuff removal from now ....

Code:
# Remove the libtool stuff
find $pkgdir -name '*.la' -delete