Bugzilla Bug 79333

Bumping the ebuild seems to work.

rox-lib-1.9.18 was just released.

rox-lib-2.0.0 released.

Created an attachment (id=58349) [edit]
rox-lib-2.0.0.ebuild

just renamed and light modified (:

Rox-Lib's homepage (http://rox.sourceforge.net/phpwiki/index.php/ROX-Lib) lists
the following dependencies:

>=dev-lang/python-2.2.0
>=rox-base/rox-2.1.0
>=dev-python/pygtk-1.99.13

This ebuild should probably reflect these...

*** Bug 95436 has been marked as a duplicate of this bug. ***

I can

I can´t see why we have three open bugs on rox-lib upgrade. 

*** This bug has been marked as a duplicate of 78309 ***

(In reply to comment #6)
> I can

(In reply to comment #6)
> I can´t see why we have three open bugs on rox-lib upgrade. 

Because my search skills suck. Reopened, sorry for bugspam. 

*** Bug 95436 has been marked as a duplicate of this bug. ***

The DEPEND should be RDEPEND since there are no compile/build-time dependencies
at all for this python library.   I also agree with the deps in comment #4.  Am
attaching a new ebuild.

Created an attachment (id=61286) [edit]
rox-lib-2.0.0.ebuild

Created an attachment (id=63628) [edit]
rox-lib-2.0.1.ebuild

version bump to 2.0.1.	ebuild attached.   

rox 2.3 has been released and could be put in ~x86. Stable ROX Lib is now
2.0.2.

Created an attachment (id=65855) [edit]
rox-lib-2.0.2.ebuild

here is a version bump ebuild for 2.0.2.  it's ~arch for all.  

can't these be added to the portage tree? what's the hold up?

dunno.  desktop devs must be behind or have other priorities.  

i think sergey must be lost in the siberian wilderness. 

What's so ironic is you just need to rename the file. No programming required.
And, you can see the blocks this bug causes.  There's another so-called
maintainer for rox, Heinrich Wendel <lanius@gentoo.org>, who I'll add to cc.
Maybe he'll get something going here? I've offered to help prepare ebuilds, but
was told I needed to become a developer. I don't want to be that. It takes too
long and is beyond what I enjoy doing and am capable of. Rox is easy so I can do
it well! LOL.

peter i am using my local portage tree to keep a lot of stuff more up-to-date
than what the gentoo base portage offers.  i mention that because there's no
reason to let the lack of an ebuild in base portage stop you.  place the current
rox-lib ebuild above into /usr/local/portage/rox-base/rox-lib; make sure you
have PORTDIR_OVERLAY=/usr/local/portage in your /etc/make.conf; make sure you
have rox-base/rox-lib ~x86 in /etc/portage/package.keywords and then:

# cd /usr/local/portage/rox-base/rox-lib
# ebuild rox-lib-2.0.2.ebuild digest
# emerge -pv rox-lib

and, if you like what you see:

# emerge rox-lib

Is there a ROX Gentoo dev anymore?

I wanted the watchers here to know that I opened a thread on the gentoo-dev
mail
list to try to ascertain what's going on and why this and other related ROX
ebuilds are not being reviewed and adopted by the maintainers. I did not get an
answer. I did get a request to become a developer and then got even more
flaming. All I and others wanted to do was to help. To alert the existing
maintainers (who, btw are active in other projects still, not awol or out of
gentoo), that new versions are out. This should not be such a problem or ardous
task. So, the short answer to this long post is that there is no resolution to
the rox issue. I tried bringing to the attention of the devs. I would recommend
that interested ROX users simply continue to pull the ebuilds down from the bug
reports or simply install ROX outside of gentoo altogether. That's what I plan
to do. This notice will be referenced in bug #78309 (rox-clib) and bug #102228
(rox 2.3).

Peter

Python modules aren't compiled. Need updated eclass

Created an attachment (id=69036) [edit]
rox-lib-2.0.2.ebuild

attached is a new ebuild for rox-lib 2.0.2 that will create the byte-compiled
.pyc files and install them alongside the .py files where rox requires them. 
you must   install the file, setup-2.0.2.py, into the rox-lib/files
subdirectory of your portage overlay.  this is the python way to create .pyc
files -- using the distutils package.  phil

Created an attachment (id=69037) [edit]
files/setup-2.0.2.py

install to rox-lib/files/setup-2.0.2.py of your portage overlay.  required for
the rox-lib-2.0.2.ebuild, in order to create .pyc byte-compiled modules
alongside the .py modules.

Thank's, the ebuild works fine, rox videothumbnail needs rox-lib greater than
2.0 to work.

Created an attachment (id=69096) [edit]
rox-lib-2.0.2.ebuild

simplified slightly.  just being anally retentive.  i know the rox.eclass will
eventually supplant this approach.  phil

(In reply to comment #25)
> Created an attachment (id=69096) [edit]
> rox-lib-2.0.2.ebuild
> 
> simplified slightly.  just being anally retentive.  i know the rox.eclass will
> eventually supplant this approach.  phil

Interestingly, rox.eclass is NOT inherited in this ebuild. This is because there
is no compiling for ROX-Lib. Just a dumb copy and merge. Being even more anal,
here is a way to utilize an ebuild class to accomplish a similar result.

Add: inherit python at the top, and change the src_install function as follows:

src_install() {
    dodir /usr/lib/
    cp -r ROX-Lib2/ ${D}/usr/lib/
    python_mod_optimize ${D}/usr/lib/ROX-Lib2/ >/dev/null 2>&1
}

the python_mod_optimize function will compile everything .py in all subdirs.
Curiously, the similar module python_mod_compile does not recurse, it only
compiles a file at a time. So, this will leave you with the pre-compiled files
(.pyc)(and the optimized (.pyo) files.

Ironically, it probably does not make any difference to rox or its applications
since most of the python apps and modules are SO small. But, IMHO, it is the
proper thing to do to compile the .py modules.

Created an attachment (id=69170) [edit]
rox-lib-2.0.2.ebuild

peter, i am in total agreement with your approach of using python_mod_optimize
from the python eclass.  that is clearly the best way to build those .pyc/.pyo
modules.  i am attaching a final version of the ebuild and obsoleting the prior
one.  i think we have beaten this horse to death now.  agreed?	phil

> i think we have beaten this horse to death now.  agreed?	phil

Agreed. Now, to get all these rox files into the tree. Sergey wrote me and said
he would get started this weekend. We will see. Thanks for your help.

rox-lib-2.0.2.ebuild is in CVS now! Thank you guys, and bug me if I forget to
move it to stable after a couple of weeks :)