You are not logged in.
Pages: 1
Topic closed
Dear all,
In my quest of the perfect todo manager, i would like to try chandler.
Not that i don't want to do it myself, but i'm not a power user and i know by experience (i tried to make some AUR before) that it will take me a lot of my time.... and i'm very busy at the moment (moving house, kid, wife, jobs, car accident to manage, etc, etc.)
So if a nice and friendly fellow could help me out in this, i'll offer him a glass of wine at my restaurant (www.provence-hz.com)
Oh and for the curious person out there, for my todo manager, i've been trying but not wholly satisfy:
- dokuwiki
- paper and pen (too easy to lose)
- taskcoach (too unstable)
- gnome todo (too simple)
If my query is too exagerated, please delete this thread...
Thank you in advance for help
Last edited by dukefeng (2008-11-08 16:52:24)
Offline
Chandler has pre-build binaries that can be run without installation. Youpi!
Anyway i'm trying to set up a nice PKGBUILD and i'm pretty stuck in many places.
It's Python based and when i check the taskcoach PKGBUILD to get some inspiration (it's a TODO manager and it's Python), it looks pretty different than the wiki tutorial on how to build up a package...
Bref, voilà the actual PKGBUILD:
# Contributor: Your Name <email@email.mail>
pkgname=chandler
pkgver=1.0.2
pkgrel=1
pkgdesc="A notebook you can organize, back up and share"
url="http://chandlerproject.org/"
arch=('i686' 'x86_64')
license=('Apache Software License, Version 2.0')
groups=()
depends=()
makedepends=()
optdepends=()
provides=()
conflicts=()
replaces=()
backup=()
options=()
install=()
source=(http://downloads.osafoundation.org/chandler/releases/1.0.2/Chandler_linux_1.0.2.tar.gz)
noextract=()
md5sums=() #generate with 'makepkg -g'
build() {
cd $srcdir/src/Chandler--$pkgver
./configure --prefix=/usr
make || return 1
make DESTDIR=$pkgdir install || return 1
}
I know i can succeed, so if nobody help me fill this up, i will eventually finish it in a certain period of time.
Offline
I'd be interested to know what you think of the current Chandler, if you try it. I didn't much like previous versions, and it ate my data a few times.
There's a book called 'Dreaming in Code', which chronicles Chandler's development (or lack of development!). It's a fascinating read, even if it's pretty much a 'how NOT to write software' manual. It reads a bit like the Spinal Tap of Software Engineering, to be honest! Still, if Chandler has put those difficulties behind it, and actually become a functioning app, I'd love to give it another shot.
Offline
Chandler has pre-build binaries that can be run without installation. Youpi!
Anyway i'm trying to set up a nice PKGBUILD and i'm pretty stuck in many places.
It's Python based and when i check the taskcoach PKGBUILD to get some inspiration (it's a TODO manager and it's Python), it looks pretty different than the wiki tutorial on how to build up a package...
Bref, voilà the actual PKGBUILD:
# Contributor: Your Name <email@email.mail> pkgname=chandler pkgver=1.0.2 pkgrel=1 pkgdesc="A notebook you can organize, back up and share" url="http://chandlerproject.org/" arch=('i686' 'x86_64') license=('Apache Software License, Version 2.0') groups=() depends=() makedepends=() optdepends=() provides=() conflicts=() replaces=() backup=() options=() install=() source=(http://downloads.osafoundation.org/chandler/releases/1.0.2/Chandler_linux_1.0.2.tar.gz) noextract=() md5sums=() #generate with 'makepkg -g' build() { cd $srcdir/src/Chandler--$pkgver ./configure --prefix=/usr make || return 1 make DESTDIR=$pkgdir install || return 1 }
I know i can succeed, so if nobody help me fill this up, i will eventually finish it in a certain period of time.
Hi.
If it is using python.
Then the makedepend and depend should python.
But please try to get more info from more experience packagers/developers here.
I am packager from another distro but I am quite new to packaging in ArchLinux
Offline
Try something like this...
pkgname=chandler
pkgver=1.0.2
pkgrel=1
pkgdesc="Command-line program to download MP3 files from Amazon.com's music store."
arch=('i686' 'x86_64')
url="http://chandlerproject.org"
license=('GPL')
depends=('python')
source=(http://downloads.osafoundation.org/chandler/releases/$pkgver/Chandler_linux_$pkgver.tar.gz)
md5sums=('f916853ee8afc189a60e18eb8a2849a8')
build() {
cd $startdir/src/
mkdir -p $pkgdir/usr/{bin,share}
mv Chandler_linux_$pkgver $pkgdir/usr/share/chandler
echo -e "#!/bin/bash\n\n/usr/share/$pkgname/chandler" >$pkgdir/usr/bin/$pkgname
chmod 755 $pkgdir/usr/bin/$pkgname
}
Offline
Well thank you Ghost1227, do you prefer Côtes du Rhone or Burgundy?
I just made a few changes and it's installing great on my laptop.
namcap propose to add alsalib as a dependency?! Should be optional isn't it?
Can some other people test this PKGBUILD in order to throw it up in the AUR?
# Contributor: Ghost1227
pkgname=chandler
pkgver=1.0.2
pkgrel=1
pkgdesc="A notebook you can organize, back up and share"
arch=('i686' 'x86_64')
url="http://chandlerproject.org"
license=('Apache')
depends=('wxgtk')
source=(http://downloads.osafoundation.org/chandler/releases/$pkgver/Chandler_linux_$pkgver.tar.gz)
md5sums=('f916853ee8afc189a60e18eb8a2849a8')
build() {
cd $startdir/src/
mkdir -p $pkgdir/usr/{bin,share}
mv Chandler_linux_$pkgver $pkgdir/usr/share/chandler
echo -e "#!/bin/bash\n\n/usr/share/$pkgname/chandler" >$pkgdir/usr/bin/$pkgname
chmod 755 $pkgdir/usr/bin/$pkgname
}
Offline
Hi all,
just cut-pasted the PKGBUILD: package built fine, Chandler ran with some warnings/errors (I think it's Chandler itself and not fault of the PKGBUILD).
I was wondering if it's good to keep a subset of the python 2.5 libs on a separate folder than use the official python ones. No experience at all in PKGBUILD writing (also with python), so I'm asking to TUs/Devs.
Cheers,
Last edited by syntaxerrormmm (2008-11-03 20:50:12)
syntaxerrormmm - Homepage
Offline
I'd be interested to know what you think of the current Chandler, if you try it. I didn't much like previous versions, and it ate my data a few times.
There's a book called 'Dreaming in Code', which chronicles Chandler's development (or lack of development!). It's a fascinating read, even if it's pretty much a 'how NOT to write software' manual. It reads a bit like the Spinal Tap of Software Engineering, to be honest! Still, if Chandler has put those difficulties behind it, and actually become a functioning app, I'd love to give it another shot.
Well, bloated, complicated, unstable, weird... I still don't get the use of Chandler....
I'm using Tasks for the moment being, It's lacking a few features to my taste, but it's doing it's simple job nicely, happy, happy.
Thanks to all the people helping with my request.
Offline
Well, bloated, complicated, unstable, weird... I still don't get the use of Chandler....
Thanks for getting back to me - sounds like Chandler hasn't changed much!
BTW, 'Dreaming in Code' (pub 2007) has the subtitle "Two dozen programmers, Three Years, 4,732 bugs, and one
Quest for Transcendent Software." It's an entertaining chronicle which (IMO) helps explain why Chandler is such a mess. After I read it, I couldn't help feeling that 1 or 2 programmers with a clear vision of what they were trying to do would have made a vastly superior product in much less time.
I'm currently using Tasks too!
Thanks again.
Offline
here is another depends:
"sdl"
o.O
Offline
I'm making a run at this. Hopefully you'll have fully working Chandler by Monday.
Res Publica Non Dominetur
Laptop: Arch x86 | Thinkpad X220 | Core i5 2410-M | 8 GB DDR3 | Sandy Bridge
Desktop: Arch x86_64 | Custom | Core i7 920 | 6 GB DDR3 | GeForce 260 GTX
Offline
Okay.... if you have a 64-bit machine you can give it a try. I have put in AUR all the necessary deps, and a chandler64 build. Building Chandler from source is akin to hitting yourself in the testicles with coils of barbed wire ... so I'm using pre-built debs (hence the 64 and 32 separate packages). I am however getting this error trying to run Chandler:
$ chandler
Traceback (most recent call last):
File "Chandler.py", line 21, in <module>
from application import Globals, Utility
File "/usr/lib/chandler/application/Globals.py", line 24, in <module>
from application.Utility import initDefaults
File "/usr/lib/chandler/application/Utility.py", line 21, in <module>
import i18n, schema, itertools
File "/usr/lib/chandler/application/schema.py", line 16, in <module>
from chandlerdb.schema.c import Redirector
File "/usr/lib/chandler/release/site-packages/chandlerdb-0.7_37-py2.5-linux-x86_64.egg/chandlerdb/__init__.py", line 4, in <module>
#
File "/usr/lib/chandler/release/site-packages/chandlerdb-0.7_37-py2.5-linux-x86_64.egg/chandlerdb/item/c.py", line 7, in <module>
File "/usr/lib/chandler/release/site-packages/chandlerdb-0.7_37-py2.5-linux-x86_64.egg/chandlerdb/item/c.py", line 6, in __bootstrap__
File "/usr/lib/chandler/release/site-packages/chandlerdb-0.7_37-py2.5-linux-x86_64.egg/chandlerdb/util/c.py", line 7, in <module>
File "/usr/lib/chandler/release/site-packages/chandlerdb-0.7_37-py2.5-linux-x86_64.egg/chandlerdb/util/c.py", line 6, in __bootstrap__
ImportError: /home/gts/.python-eggs/chandlerdb-0.7_37-py2.5-linux-x86_64.egg-tmp/chandlerdb/util/c.so: undefined symbol: PyUnicodeUCS4_AsUTF8String
Any clues? If anybody is interested in Chandler on 32-bit, let me know and I'll push 32-bit versions of chandler and the python-pylucene dependency before investigating this further.
Res Publica Non Dominetur
Laptop: Arch x86 | Thinkpad X220 | Core i5 2410-M | 8 GB DDR3 | Sandy Bridge
Desktop: Arch x86_64 | Custom | Core i7 920 | 6 GB DDR3 | GeForce 260 GTX
Offline
Looks like we're at a roadblock waiting on upstream:
Res Publica Non Dominetur
Laptop: Arch x86 | Thinkpad X220 | Core i5 2410-M | 8 GB DDR3 | Sandy Bridge
Desktop: Arch x86_64 | Custom | Core i7 920 | 6 GB DDR3 | GeForce 260 GTX
Offline
ImportError: /home/gts/.python-eggs/chandlerdb-0.7_37-py2.5-linux-x86_64.egg-tmp/chandlerdb/util/c.so: undefined symbol: PyUnicodeUCS4_AsUTF8String
Any clues?
Maybe this helps:
http://lists.osafoundation.org/pipermai … 03785.html
Offline
Offline
Pages: 1
Topic closed