Here is an ebuild for the new Quanta-BE-1 version of the web editor for KDE. I've set a dependancy for the quanta-docs ebuild currently in portage. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 21697 [details] Ebuild for quanta-BE-1 I wasn't sure what version to name the ebuild, but here it is.
Wouldn't it be better to name it quanta-3.2.1_alpha1 or something like this instead having two different ebuilds in .../app-editors/quanta/ and .../app-editors/quanta-BE/ which would need to block each other? Named branches doesn't really fit in the portage ebuild naming scheme. -> http://www.gentoo.org/doc/en/gentoo-howto.xml#doc_chap2
I agree that it shouldn't be a seperate package from the base Quanta package since they would likely conflict. However, I don't think "alpha" quite describes the bleeding edge releases accurately. To me, "alpha" implies a possibly unstable testing release. According to: http://quanta.sourceforge.net/main2.php?newsfile=qberelease01 "There are known bugs and unfinished features. however any time we release a BE package you can be sure that it has been tested by a number of users and developers. It has been found to be usable for daily work and stable. We intentionally avoid any serious changes or updates that can destablise the build for several weeks prior to relaese." To me it sounds more like a beta or a pre-release, even. Carlo, I understand that you just suggested "alpha1" as an example, but I wanted to throw my $0.02 in before it got too far along.
I was thinking about releasing the ebuild as a normal quanta ebuild, but versioned as 3.2.0_pre2003xxxx. The reason I'm hesitant is that quanta-be1 is pretty old...was hoping they'd have another be release to do this with.
be2 is in portage now.
