Hi! Attached you'll find a ebuild for glcu (gentoo linux cron update). glcu - gentoo linux cron update is a rich featured program that semi-automatically updates your gentoo box. glcu runs in the night via cron, prebuilds new packages and sends you an eMail if there are new packages available. The eMail provides also an easy command to fully update the gentoo box and information about the prebuilding processes. glcu evolved from a bash script to a python version. More information about glcu can be found on its webpage: http://glcu.sourceforge.net/ And in the gentoo forums: http://forums.gentoo.org/viewtopic-p-2123630.html I would like to get glcu into the portage tree to make the installation and update of glcu easier and to get more testers. Thanks and bye, Michael Reproducible: Always Steps to Reproduce:
Created attachment 65507 [details] glcu-0.9.7.ebuild (New package)
Created attachment 65508 [details] glcu-0.9.7.ebuild (New package)
Comment on attachment 65508 [details] glcu-0.9.7.ebuild (New package) I just forget to tick the 'text/plain' box for the first ebuild :-(
Comment on attachment 65508 [details] glcu-0.9.7.ebuild (New package) I just forgot to tick the 'text/plain' box for the first ebuild :-(
Hi! I just released version 0.9.7.1 of glcu, so please just change the name of the ebuild to 'glcu-0.9.7.1.ebuild'. This will soon become the stable tree of glcu. Together with another developer, we will also create an even better version of glcu that will use the portage API for the operations and will be even mor customizable. In order to get more feedback and more testers, I would like to get glcu into portage, but if you think it's not ready yet, just say/write so. Thanks and bye, Michael
some notes: - whats the point of putting the .py into /usr/lib ? just do `newbin glcu.py glcu` and then symlink it into /etc/cron.daily - put the config file at /etc/glcu.conf ... /etc/conf.d is for init.d scripts only - the esearch/eix flags are fluff ... just put docs into your config file that read 'you need to emerge esearch / exi first before using BLAH options'
(In reply to comment #6) Thanks for your suggestions, SpanKY, > some notes: > - whats the point of putting the .py into /usr/lib ? just do `newbin glcu.py > glcu` and then symlink it into /etc/cron.daily I will do that - I'm just not very experienced in writing new ebuild. > - put the config file at /etc/glcu.conf ... /etc/conf.d is for init.d scripts only Good to know. Because the configuration will change a bit in future version I will put alle config files in an /etc/glcu directory. Hope thats fine. > - the esearch/eix flags are fluff ... just put docs into your config file that > read 'you need to emerge esearch / exi first before using BLAH options' OK, I had it that way in the beginning. It probably is overkill to have USE flags for it... Bye, Michael
sure, you can use /etc/glcu as long as you plan on having more than one file in it
I've been testing this for a few weeks, perhaps even a couple of months now - it's great. I've just found a bug though, as soon as it's fixed I don't see why this can't go into portage?
(In reply to comment #9) > I've been testing this for a few weeks, perhaps even a couple of months now - > it's great. I've just found a bug though, as soon as it's fixed I don't see > why this can't go into portage? > did the bug ever get fixed? what was it? even with the bug couldn't it be included in portage hard masked if necessary?
(In reply to comment #10) > did the bug ever get fixed? what was it? even with the bug couldn't it be > included in portage hard masked if necessary? I didn't fix the bug, because I startet to rewrite this application to make it real OO. I'm half way through with it, but it will take several more months until I will find the time to complete it (any help is appreciated). Therefore I wouldn't advise to put version 0.9.7.1 into portage (it works with portage-2.1, but isn't well tested at all). As soon as there is a new version, I will come back here. Michael
Michael, whats the status on development?
(In reply to comment #12) > Michael, whats the status on development? I'm sorry to say, I don't know, when I can finish the next version. I'm half way through, but didn't had time to do anything in the last half year. I'm happy that version 0.9.7.1 is still working very good, cause I will need at least several more months till I can finish 0.9.8 (too many other things to do...) I appreciate anyone who wants to help.
Seems the recent Python update now causes a deprecation warning: glcu:17: DeprecationWarning: The sre module is deprecated, please import re. Will changing "sre" to "re" fix this?
Created attachment 162456 [details] updated ebuild for Version 0.9.7.2 This is a new ebuild for a new version. Although I don't think I will ever finish the rewrite of glcu (I tried for three years now ;-), I made a new version, that hopefully works as well, as the last one for three years :-) I changed the ebuild too, so I hope everything is fine now. The changes are: - glcu config file is now: /etc/glcu.conf - fixed bug with predictable tmp-filecreation - switched python sre module to re - a few minor changes to enhance glcu I hope everything works fine, and would appreciate any comments - preferable positive ones in the gentoo-forum ;-)
The output module now also generates a deprecation warning: # /etc/cron.daily/glcu /usr/lib/portage/pym/output.py:45: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output /etc/cron.daily/glcu:20: DeprecationWarning: the sets module is deprecated
Also update-eix has been renamed to eix-update :-) # equery files eix [ Searching for packages matching eix... ] * Contents of app-portage/eix-0.20.5: /etc /etc/eixrc /usr /usr/bin /usr/bin/eix /usr/bin/eix-diff -> eix /usr/bin/eix-functions.sh /usr/bin/eix-layman /usr/bin/eix-remote /usr/bin/eix-sync /usr/bin/eix-test-obsolete /usr/bin/eix-update -> eix /usr/bin/versionsort -> eix /usr/share /usr/share/doc /usr/share/doc/eix-0.20.5 /usr/share/doc/eix-0.20.5/AUTHORS.bz2 /usr/share/doc/eix-0.20.5/ChangeLog.bz2 /usr/share/doc/eix-0.20.5/eix-db.txt.bz2 /usr/share/doc/eix-0.20.5/eix-xml.txt.bz2 /usr/share/doc/eix-0.20.5/html /usr/share/doc/eix-0.20.5/html/eix-xml.xsd /usr/share/man /usr/share/man/man1 /usr/share/man/man1/eix.1.bz2 #
