To not clutter the 'orphaned packages in community' thread, I created a new one for discussing the e17 packages.
As I have not yet heard something from reverie and I had some free time today, I decided to take a closer look to e17 (he is of course still free to contact me). Currently provided as orphans in community are snapshots. The latest e17 snapshot release has been August 2007 (the ones in community are one or two months older). This means that updating e17 to the latest snapshots still gives as an outdated version of e17. I did not find anything on the e17 mailing lists on when new snapshots will be provided, or why there are not updated anymore.
So what have I done. I created all core e17 CVS packages from scratch and wrote a build script to easy update them all with just one command. I've been running them for the last 5 hours or so, and everything seems to work stable. I think it would not hurt if the CVS packages would come in place of the snapshots in community as it is not sure when, or even if the snapshots will be updated in the near future.
If somebody is against, please speak.
Also, I need somebody to at least test building it for x86_64 to check if I can safely use Aaron's build machine (I will contact him if so), or that I should better find someone to update it for x86_64.
HOWTO TEST: Get the archive with all PKGBUILDs and the buildscript from http://pressh.googlepages.com/e17-cvs-pkgbuilds.tar.gz. Make sure you configure pacman to work with sudo before executing the buildscript (see the script for further details).
For anybody else willing to test, you can add the following to your pacman.conf
[e17-cvs] Server = http://pressh.googlepages.com/
Install the i686 versions with 'pacman -Sy e17-cvs'
Thanks for your time!
To reply to my previous message in this thread, there is no need to testbuild the e17-cvs PKGBUILDs with the script I supplied yesterday anymore. I did found somebody on IRC today who was willing to do it. No errors during the build process came up as he reported.
I will test some additional modules and see which ones are stable enough to be of any use, and will push those into community after updating the wiki.
Time for a little update on this subject.
After my last e-mail on this subject, Reverie (the guy from the unofficial e17 [takhis] repo) responded to my mail. As he has not much time on his hands, he is happy for me maintaining it in [community], as he says.
I also asked him if it would be best to have the 'stable' snapshots or the cvs versions in [community]. As he responds there is no such thing as stable snapshots. These snapshots are created whenever the e17 dev feels like it, sometimes even during api changes. Besides that, the available themes and such do only work with the cvs versions.
Well, that's the most relevant information for you guys, the rest he mails is on some deprecated deps an such.
How I will go from here ? As you may have noticed I've uploaded e17-cvs packages to [community] somewhere last week. This is for i686 only at the moment. For the x86_64 builds I'm struggling with Aaron's build machine though it is not working out yet. An e17 x86_64 user has offered me his help by creating a build environment for me on his workstation, though we're not quite sure yet how to do so. He has created a thread on bbs about this here: http://bbs.archlinux.org/viewtopic.php?id=42545 Feel free to pop in on that subject if you have any hints.
If we succeed to set up this 64bit build environment, all I have to do is run a couple of scripts in there and everything should go automagically.
For the current snapshots, I'm still not sure if to put them into unsupported, or to delete them altogether. If they go into unsupported the prefix should be changed to /usr (currently it installs in /opt/e17).
That's all about e17 atm.
ps. Tomorrow I should find time on posting the 'to be removed' list for the orphaned packages in community. I'll recheck all deps before doing so.
Ronald
On Sun, 20 Jan 2008, Ronald van Haren wrote:
Time for a little update on this subject.
After my last e-mail on this subject, Reverie (the guy from the unofficial e17 [takhis] repo) responded to my mail. As he has not much time on his hands, he is happy for me maintaining it in [community], as he says.
I also asked him if it would be best to have the 'stable' snapshots or the cvs versions in [community]. As he responds there is no such thing as stable snapshots. These snapshots are created whenever the e17 dev feels like it, sometimes even during api changes. Besides that, the available themes and such do only work with the cvs versions.
Well, that's the most relevant information for you guys, the rest he mails is on some deprecated deps an such.
How I will go from here ? As you may have noticed I've uploaded e17-cvs packages to [community] somewhere last week. This is for i686 only at the moment. For the x86_64 builds I'm struggling with Aaron's build machine though it is not working out yet. An e17 x86_64 user has offered me his help by creating a build environment for me on his workstation, though we're not quite sure yet how to do so. He has created a thread on bbs about this here: http://bbs.archlinux.org/viewtopic.php?id=42545 Feel free to pop in on that subject if you have any hints.
If we succeed to set up this 64bit build environment, all I have to do is run a couple of scripts in there and everything should go automagically.
I could build them. Just send me the scripts and the list of packages.
For the current snapshots, I'm still not sure if to put them into unsupported, or to delete them altogether. If they go into unsupported the prefix should be changed to /usr (currently it installs in /opt/e17).
I would just delete them. If not, put them 'as is' in unsupported. The next maintainer will fix them.
That's all about e17 atm.
ps. Tomorrow I should find time on posting the 'to be removed' list for the orphaned packages in community. I'll recheck all deps before doing so.
Yesterday, I moved adns from extra to community. So it's one more orphan that needs to remain in community.
Ronald
On Sun, 20 Jan 2008 18:01:53 +0100 "Ronald van Haren" pressh@gmail.com wrote:
How I will go from here ? As you may have noticed I've uploaded e17-cvs packages to [community] somewhere last week. This is for i686 only at the moment. For the x86_64 builds I'm struggling with Aaron's build machine though it is not working out yet.
For mee Aaron's machine is working well; if you tag arch64-bit your package (I think all -cvs marked here http://dev.archlinux.org/~andyrtr/pkg_diff.html with a blank field on 64 bit column ) I can run a script that compile them. How tag? I think, from http://wiki.archlinux.org/index.php/Arch64_FAQ #How_can_I_patch_existing_PKGBUILDs_for_use_with_Arch64.3F ( section for the devs ) you need to do these commands. Until confirmation, do nothing :)
On Jan 21, 2008 5:03 PM, JJDaNiMoTh jjdanimoth@gmail.com wrote:
On Sun, 20 Jan 2008 18:01:53 +0100 "Ronald van Haren" pressh@gmail.com wrote:
How I will go from here ? As you may have noticed I've uploaded e17-cvs packages to [community] somewhere last week. This is for i686 only at the moment. For the x86_64 builds I'm struggling with Aaron's build machine though it is not working out yet.
For mee Aaron's machine is working well; if you tag arch64-bit your package (I think all -cvs marked here http://dev.archlinux.org/~andyrtr/pkg_diff.html with a blank field on 64 bit column ) I can run a script that compile them. How tag? I think, from http://wiki.archlinux.org/index.php/Arch64_FAQ #How_can_I_patch_existing_PKGBUILDs_for_use_with_Arch64.3F ( section for the devs ) you need to do these commands. Until confirmation, do nothing :)
-- JJDaNiMoTh - ArchLinux Trusted User
Maybe I should have been a bit more clear. The problem is not the actual compiling, that works great (I've been able to build a couple of packages). The problem is with the dependencies between the packages. Almost each next package depends on the previous one. I tried building those packages with using the 'SRCROOT' variable, though I could not get that to work.
Finally I just started to build each package, upload it, wait for the build machine to sync, build the next one, etc. That just is not doable being it CVS packages which change daily.
I've sent my current scripts and PKGBUILDs to Eric (I still need to rewrite them to use the CVS sources), as he said in this thread a would be able to build it. So I think e17-cvs should be covered for now.
Thanks for your offer though. If I need it in the future I'll let you know.
aur-general@lists.archlinux.org