Lazarus 0.9.7 Released: http://sourceforge.net/project/showfiles.php?group_id=89339 Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Install Lazarus 0.9.7
Created attachment 63750 [details] Lazarus 0.9.7 Test Ebuild Changed the existing ebuild file: Changed SRC_URI to reflect the new file (called lazarus-050702.tgz) and changed DEPEND for updated fpc dependencies: DEPEND="=dev-lang/fpc-2.0.0-r1 =dev-lang/fpc-source-2.0.0 >=media-libs/gdk-pixbuf-0.22.0-r3 net-misc/rsync"
*** Bug 99482 has been marked as a duplicate of this bug. ***
i'll work on this at the weekend if noone is faster, didnt note the new release before. please use the ebuild from bug #87934 instead of the one taken from portage. change it's DEPEND-part from -------------------- DEPEND="=dev-lang/fpc-2.0.0-r1 =dev-lang/fpc-source-2.0.0 >=media-libs/gdk-pixbuf-0.22.0-r3 net-misc/rsync" RDEPEND="${DEPEND}" ------------------ to this ------------------ RDEPEND="=dev-lang/fpc-2.0.0-r1 =dev-lang/fpc-source-2.0.0 >=media-libs/gdk-pixbuf-0.22.0-r3 net-misc/rsync" DEPEND="${RDEPEND} net-misc" todo: check the officially needed gdk-pixbuf version
err. forget about the depend thingy. this one's what i meant to write: RDEPEND="=dev-lang/fpc-2.0.0-r1 =dev-lang/fpc-source-2.0.0 >=media-libs/gdk-pixbuf-0.22.0-r3" DEPEND="${RDEPEND} net-misc/rsync" reason for the change is that lazarus doesnt need rsync while it's installed, but the ebuild does during installation.
(In reply to comment #0) > Lazarus 0.9.7 Released: > http://sourceforge.net/project/showfiles.php?group_id=89339 Well, Lazarus 0.9.8 is released now, shall we create a new issue or continue discussion in this one? Regards: Uwe Fechner
(In reply to comment #5) > (In reply to comment #0) > > Lazarus 0.9.7 Released: > > http://sourceforge.net/project/showfiles.php?group_id=89339 > > Well, Lazarus 0.9.8 is released now, shall we create a new issue or continue > discussion in this one? > > Regards: > > Uwe Fechner I'm not sure of general policy when it comes to these things - but considering that the 0.9.7 release seems to have been completely removed from the SourceForge webpage there doesn't seem to be any point in have a 0.9.7 ebuild for a non-existant file. See: http://sourceforge.net/project/showfiles.php?group_id=89339
To the bug owner: Please close this bug. I created a new one (Bug 99991) for lazarus 0.9.8
*** Bug 99991 has been marked as a duplicate of this bug. ***
n.m.odd is a developer release n.m.even is a "normal" release in total analogy to the linux kernel, as i understand it - but dont quote me on that... so for example: 0.9.7 isnt meant for the masses, but 0.9.6 and 0.9.8 are. you see? now what about the general rule in such a case concerning the bug? i cannot understand why Jakub Moc marked the other one as a duplicate. i'd close that one and open a new one, but since he did that on purpose that seems to be the rule and i suggest you change the title, AndrewB? I'll look for this piece within the next 24h to get it ready to rumble with 0.9.8 with maybe or maybe not a quick look to support amd64 with upcoming new fpc ebuild series. so long
Created attachment 64204 [details] lazarus-0.9.8.ebuild test #1 makes previous ebuild obsolete. indirect issues: see bug #100131
Hello, your lazarus-0.9.8 ebuild works like a charm. Only thing I had to do is to set the fpc source dir to: /usr/lib/fpc/src/fpc/ to make Lazarus happy, perhaps this could be documented a little bit better. Thanks a lot: Uwe Fechner
In reply to comment #11, Uwe: See bug number 100131 for that, this bug is set to depend on it - it's for exaclty that purpose.
Lazarus 0.9.10 now in portage which solves a pile of other bugs too and works with fpc 2.0.0.
