The last released anjuta version (1.0.2) is still using gnome 1.4, while most people using gentoo are already using gnome 2 instead, for a long time. I'd like to share the ebuild I'm using to get anjuta from cvs, it is pretty stable. Reproducible: Always Steps to Reproduce: Actual Results: it works for me ;-)
Created attachment 11723 [details] A well tested ebuild for anjuta cvs up to 20030414 12:00 GMT. You can rename it to any "anjuta-1.2.0_pre<data>.ebuild" for newer versions. This is the best tested ebuild I have of anjuta cvs. I have more recent ones (just rename the file to another date for that), but I haven't tested them as good as this one. This is my first ebuild I'm submitting, I just want to be sure it works!
we don't want to maintain cvs ebuilds without a real need (anjuta1 is still far better than anjuta2 in many ways). If i want a snapshot i would do a real one, not one stressing cvs unneeded. We might do a cvs snapshot at a certain point when no betas get released, but not right now.
There is a *HUGE* difference indeed between anjuta and anjuta2. Anjuta2 is a badly chosen rename of the gIDE project. There is no real relation between anjuta and anjuta2, both are being developed for GTK2/Gnome2. FYI, I'm talking about anjuta "1", if you had read this a little better, you'd know that. The upcoming anjuta 1.2.0 will be based upon GTK2/Gnome2. I'll just supply an ebuild when it is released. I see Gentoo as a very well suited software-development distro, so I think people may find this ebuild useful... I'm actually wondering why the anjuta-1.0.2 ebuild still even contains the KEYWORDS tag, as if it isn't stable... I think it would be more in place to have a dated-cvs ebuild with this "unstable" tag.
alright .. no need to get worked up about this. just as you were writing that comment, anjuta just released their anjuta gtk2 beta 1.1.1. so if i read correctly, this is "anjuta2", is it not? if so, then it is perhaps better that we have an ebuild for anjuta 1.1.1 rather than a cvs ebuilds/snapshots. the problem with cvs ebuilds is that they are a nightmare to support. a checkout one day can compile and on another it could break on everything. there is no real way to do any QA. we (at least the gnome team) are reluctant to support any cvs ebuilds unless there is a extraordinary high demand for such things. even then, we will usually only consider supporting a cvs snapshot in the tree. finally, you have a valid point about anjuta 1.0.2 being marked as ~x86. to clarify things, ~x86 doesn't mean it is unstable, it means it is _untested_. all ebuilds committed to the tree need to be in ~x86 for a certain amount of time before it is marked as stable. we'll consider marking that stable shortly. keep in mind that the ~x86 means the ebuild is "unstable" rather than the actual application/product/package.
(not worked up) I 've just been able to read my recent anjuta-dev digests, and it seems indeed that the once called "1.2.0 alpha" has been renamed to 1.1.1 beta, funny... The about box of the cvs version has always said "anjuta 1.2.0" since the first gtk2/gnome2 branch. Exactly because "a checkout one day can compile and on another it could break on everything", I have made a time-stamped ebuild of a certain date/time (20030414 12:00 GMT) that I've tested thouroughly. The problem with most cvs ebuild is that is it still depending on the users (cvs checkout side) timezone, I think others should follow this example. Anyway, I'm puzzled why Naba released a beta, right after some big changes that still need testing... Hopefully, we're heading towards a freeze *finally*, I just hope it's going to be stable.
