Several core ROX programs are out of date. Rox bug # 102228 Rox-lib bug # 79333 Rox-clib bug # 78309
Despite the above bug reports, and copies to the current listed maintainers, the products are not being updated. Rox is among the easiest programs to maintain, and many ebuilds simply need to be renamed in order to work. In addition, I and others have contributed ebuilds for consideration, and they continue to languish or are assigned to the maintainer-wanted alias. I have offered to produce ebuilds for review and submission. I was told I needed to become a developer. While I would be happy to take on the responsibility, I don't see why it would be necessary. The ebuilds are already there for you. Just search ROX in bugzilla. I don't need my name on it. However, I do feel strongly that if you are going to offer a package suite in portage, you have an obligation to keep it current -- ESPECIALLY when the user community is doing the work already. No one is asking for any special work to be done -- just that bugs are responded to and handled. I do not know what happened to the listed rox maintainers, svyatogor and lanius or why they are not updating rox. I was wondering what it will take to have the portage tree updated. With the two libraries noted above, they are blockers to some of the rox applications and really need to be resolved. At least have the rox bugs reviewed and cleared out. Most of the ebuilds have already been submitted and are being used. They deserve to be placed in portage. -- Peter -- [email protected] mailing list
