You are not logged in.
Snowman > OK got it & will apply these advices.
Thank you so much for helping me on my 1st PKGBUILD
Here is opera-devel PKGBUILD that do NOT replace Opera stable release :
# Contributor: kozaki <kozaki.dev@free.fr>
pkgname=opera-devel
pkgver=9.0
pkgrel=1
pkgdesc="The Opera web browser Preview-1 (beta) version"
depends=('x-server' 'lesstif' 'qt')
source=(http://snapshot.opera.com/unix/9.0-Preview-1/intel-linux/opera-9.0-20051020.6-shared-qt.i386-en.tar.gz)
url="http://www.opera.com/"
md5sums=('fe67a740e0825e03b874e1b8add02c4c')
build() {
cd $startdir/src/opera-9.0-20051020.6-shared-qt.i386-en
sed -i 's|str_defaultprefix="/usr"|str_defaultprefix="/opt/opera"|' install.sh
./install.sh DESTDIR=$startdir/pkg
mkdir -p $startdir/pkg/usr/bin/
ln -s /opt/opera/bin/opera $startdir/pkg/usr/bin/opera-devel
sed 's=libXm.so.3=libXm.so.2=' -i $startdir/pkg/opt/opera/lib/opera/plugins/operamotifwrapper-3
}
Note that I found no way to change opera-devel user directory (~/.opera), thereafter you'll have to disable mail/news in the devel-version if you want to keep your mails/news with the stable version.
Test I did with another user show no visible improvment in this location anyway.
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
Thank you so much for helping me on my 1st PKGBUILD
De rien. 8)
Offline
Sorry to change it so soon.
I've seen wain & saintshakajin mentionned adding an icon and a desktop entry for KDE on the French forum. So i thought it might be fun to try with a nice icon & a kde menu entry
# Contributor: kozaki <kozaki.dev@free.fr>
pkgname=opera-devel
pkgver=9.0
pkgrel=1
pkgdesc="The Opera web browser Preview-1 (beta) version"
depends=('x-server' 'lesstif' 'qt')
source=(http://snapshot.opera.com/unix/9.0-Preview-1/intel-linux/opera-9.0-20051020.6-shared-qt.i386-en.tar.gz
http://kfm-caen.fr/arch/opera.png
http://kfm-caen.fr/arch/opera.desktop
)
url="http://www.opera.com/"
md5sums=('fe67a740e0825e03b874e1b8add02c4c'
'bacc2ddbcac3c841e06229d0b4e9ed5d'
'43e24f3fbbaff4d22267f2935ad939ff'
)
build() {
cd $startdir/src/opera-9.0-20051020.6-shared-qt.i386-en
sed -i 's|str_defaultprefix="/usr"|str_defaultprefix="/opt/opera"|' install.sh
./install.sh DESTDIR=$startdir/pkg
mkdir -p $startdir/pkg/usr/bin/
ln -s /opt/opera/bin/opera $startdir/pkg/usr/bin/opera-devel
sed 's=libXm.so.3=libXm.so.2=' -i $startdir/pkg/opt/opera/lib/opera/plugins/operamotifwrapper-3
mkdir -p $startdir/pkg/usr/share/{applications,pixmaps}
install -m644 $startdir/src/opera.png $startdir/pkg/usr/share/pixmaps/
install -m644 $startdir/src/opera.desktop $startdir/pkg/usr/share/applications/
}
Try it (at your own risk) as you want ; works fine in this location.
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
A very useful command is:
makepkg -c 2>&1 | tee build.lst
After the build you can inspect the build.lst file for any warning/error that you have missed during the build process.
I'm curious as to what the difference is between:
makepkg -c 2>&1 | tee build.lst
and
makepkg -c 2>&1 > build.lst
I brought up the man page for tee and it says, "Copy standard input to each FILE, and also to standard output.", but isn't that the same as "2>&1 > foo"?
Correct me if I'm wrong. Is the difference that using the former you get to see the standard error and standard input both in the file and on the terminal screen, and the latter you only see standard error and standard output just in the file?
Can someone clarify this. I think I may be missing something.
Offline
Nice thanks!
I dont undertand why install fakeroot i dont see where do you use fakeroot.
Cheers!
Offline
You need fakeroot to be able to build packages as a regular user which is the recommended way. To use it, make sure you have
export USE_FAKEROOT="y"
in /etc/makepkg.conf and makepkg will use it automatically.
Offline
Thanks for this thread.I was struggling with "makepkg -s" options.(I DONT want to install sudo jfyi).
now @OP helped me!:D
Offline
I would care to read some info regarding where to put the different stuff. Now I have aptana, firefox and openoffice in /opt, but why are they there, and the rest elsewhere.
Birger
Offline