Layman-2.0 development testing

dol-sen · Posted: Thu Aug 11, 2011 2:42 pm Post subject:

OK, I have a final layman-2.0.0_rc2 and an updated layman-9999 ebuilds in the gentoo-guis overlay. Both waiting to/should be pushed to the tree before long.

For layman-9999 users, you will need the new layman-9999 ebuild as both the source and ebuild are now setting EPREFIX at install. So that means layman-9999 can now be installed in an eprefix environment. If you are running the git clone code directly in the checkout it will only work if it is not an eprefix environment, it defaults to a normal '/'.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Thu Aug 25, 2011 5:13 am Post subject:

For those using layman-9999. I've been changing some config variable names. 'local_list' is changed to 'installed' and I've changed the default filename to installed. So either change the /var/lib/layman/overlays.xml file to /var/lib/layman/installed/xml or change the config to use the overlays.xml name. That change should help prevent confusion with the overlays config variable.

I created some code to migrate it automatically (provided you didn't stray from the defaults) but it prevented all the tests from passing.

I don't know yet how i'm going to handle it for everyone yet.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sat Sep 17, 2011 11:52 pm Post subject:

Layman-2.0.0_rc3 has been pushed to the tree. This should likely (hopefully) be the last rc. There have been very few bugs reported overall, so i am pleased.

Note both the _rc3 and -9999 ebuilds have been changed to rename your existing installed db xml file from overlays.xml to installed.xml. This should be less confusing for people working/changing things in the layman.cfg file.
oops. just remembered I hadn't updated the doc/manpage for the variable name & filename change.

Well, it'll be in the final.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

firephoto · Posted: Mon Sep 19, 2011 6:39 pm Post subject:

fyi rc3 today broke something. "layman -l" doesn't show any overlays but the overlays.xml file does exist with the old entries.

This is with:

storage : /usr/local/portage/layman

*edited..

I misread your post, so what has happened is the overlays.xml was not copied to installed xml. Related to the non-default overlay location (original location) I suppose.
_________________
#gentoo-kde on freenode

dol-sen · Posted: Mon Sep 19, 2011 11:20 pm Post subject:

firephoto. You are correct. the ebuild could not handle the change from the non-default cfg setting. So edit the /etc/layman/layman.cfg's installed variable so it points to the correct location. You might even rename it from overlays.xml to installed.xml if you like or just edit it to the existing filename. This change was made to stop some confusion, reported by some people.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Mon Sep 26, 2011 1:38 am Post subject:

So, looks of it, I'll release another rc. So #4 should be coming soon. It looks like I've made good progress at fixing the differences between py2 and py3. A few more changes and I hopefully can just run python's 2to3 update tool to update the code and layman should be able to install/run in python3.

I've been able to successfully run the tests in python3 now. I need to backport as many of the (non 2to3 made) changes to the normal codebase as possible. Hopefully I should end up with only a small patch file to update the doctests which 2to3 does not update in its run.

As much as I would love to get a 2.0.0 final release out, I would also like to hold it off to have layman fully python-2 and python-3 compatible.

Question I have for you people is, would you prefer I put out a 2.0.0 release now (meaning very soon with the current code) or wait a bit longer to test out layman in python-3 first?
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

zoolook · n00b Joined: 05 Oct 2002 Posts: 16

dol-sen · Posted: Thu Dec 22, 2011 3:04 am Post subject:

I have it mostly ready to run on python 3. But I've been sidetracked lately, and haven't gotten around to one more fix for an rc4 which should become 2.0.0 final. The python 3 changes will come after that. Also for python 3, the ebuild will need to run 2to3 on the code. All attempts at making the code py2 and py3 compatible failed. If I got it woking in py3, it broke py2 and vice-versa. I need to do some more testing and probably a few more changes for it to work in py2 and have a clean 2to3 run without additional patching.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...