This looks promising. Open-standards, works with iCalendar clients. http://www.schooltool.org/schoolbell Reproducible: Always Steps to Reproduce:
Hmm, seems to need Zope 3 (not in portage yet)...
zope3 is in portage :) check it under net-zope/zopex3
(In reply to comment #2) Oh well - what a strategic move, well hidden! :-)
Before we put this package into portage, we need more info from users, that this package is really wanted/usefull/needed. Without such votes, we can'not put it in, because of increasing workload on net-zope devs to support small/seldom use package. PLease consider using portage overlays (PORTDIR_OVERLAY in /etc/make.conf) and use package personally.
Well, I am running v0.8 (or so) here since a few month and I am using it on a daily basis. It is pretty neat and I *really* like to see an ebuild for this one. Unfortunately it doesn't look like an "easy-to-do" one for a first-time ebuild. And using portage overlays without an existing ebuild ???
Guys, anyone willing to prepare ebuild for newest version? zope-3.1.0 is in portage (net-zope/zope/zope-3.1.0) if yes, please provide an ebuild and reopen bug.
Created attachment 77694 [details] schoolbell-1.2.3.ebuild, first try OK, take this ebuild as a starting point. It installs fine here and includes an init.d script and an adjusted config file, but I haven't testing it too much with 'real data' though. All data is still stored in the dir where schoolbell has been started in, so this will be '/' if you start it on default. I guess there is some pace for enhancements. Additionally the daemon would be started as root and I am not sure if there is a better way (and how this would be done). Starting schoolbell with the init.d script usesg '--background', so it says [OK] even it takes a few more seconds to start up. (and btw. I have no clue about Zope so I really do not know what I am doing :) ).
Created attachment 77695 [details] init.d/schoolbell file the init.d/schoolbell file, to be put into the files directory
Created attachment 77696 [details] /etc/schoolbell.conf the adjusted schoolbell config file, to be put into the files directory (will be installed as /etc/schoolbell.conf)
reopen ber Bjoern request.
Hello, I am using zopex3 because I seem unable of having zope-3 up and runnig. I have the impression that in /etc/schoolbell.conf you need to change <filestorage> path Data.fs </filestorage> to <filestorage> path /usr/share/zproduct/schoolbell-1.2.3/Data.fs </filestorage> otherwise the Data.fs would be created in the directory from where you called /etc/init.d/schoolbell start. I apologize in advance if this problem is due to my wrong zope install.
Created attachment 82463 [details] schoolbell-1.2.4.ebuild New version out (1.2.4), new try :). Please find enclosed the ebuild for schoolbell-1.2.4 and the new config and init.d files (following). Everything has been changed to use /usr/share/zproduct/schoolbell (a link being made by the zope eclass ?), and now the Data files will be created accordingly (thanks for the hint). Just one problem left: when updating to a newer version the Data files will still be in the directory of the older version and the link will be changed to the new version. So the files will have to be copied to the new dir by the user/admin. Don't know how to solve this, but I am thinking about using a new seperate dir (like e.g. /usr/share/zproduct/schoolbell_data) for the data files. But I've got no idea if this is a 'good way' to solve the problem nor if it is gentoo or zope conform (or whatever).
Created attachment 82464 [details] init.d/schoolbell file for 1.2.4
Created attachment 82465 [details] /etc/schoolbell.conf for 1.2.4
Bjoern, let me provide You a few hints for cleaning this: 1. There should be additional pkg_config() function in ebuild 2. datads, logs, and config should be located in /var/lib/schoolbell/{var,logs,etc} directories 3. also it should use slot for "1.2" i suppose 4. pkg_config should create whole /var/lib/schoolbel instance directory, while normal emerge should provide general infor what should be done next 5. please pay attention, that no 'unversioned' symlink should be created in the /usr/share/zproduct, it has to be solved by proper links to the /usr from /var instance - you can use ebuild variables and sed over conf files to achieve this.
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
