[clc-devel] proposal - prt-check
Hi, I know I'm new and should not be to loud. ;-) But I had a idea which I would like to propose. I hope you'll not catch it wrong.. The prt-check script I wanna write should check the availability of each port which has set the (new) tag "Check" to on and write warning mails to its maintainer if something goes wrong. So, the maintainer could decide if he/she gets warnings when something goes wrong with its port or not. This is just an idea and I would propose to write it in python. Cheers, Daniel -- Daniel K. Gebhart http://informatik.uibk.ac.at/users/c703263/ Institute for Computer Science University of Innsbruck Fon: (office): +43 512 507 6490 Mail: <daniel.gebhart(at)uibk.ac.at>
On Wed, 15 Oct 2003 21:27:25 +0200 "Daniel K. Gebhart" <dkg@con-fuse.org> wrote:
Hi,
Hi Daniel,
I know I'm new and should not be to loud. ;-) But I had a idea which I would like to propose. I hope you'll not catch it wrong..
It's always good to hear new ideas.
The prt-check script I wanna write should check the availability of each port which has set the (new) tag "Check" to on and write warning mails to its maintainer if something goes wrong. So, the maintainer could decide if he/she gets warnings when something goes wrong with its port or not.
What do you mean by 'availability'? Would the script only check for availability of source() files, or try to build the port? In both cases, I'd prefer not to add another tag to Pkgfile, I suggest an (independent) external list or something similar. Or, better again, the script could periodically check all ports and submit problems to the maintainers who want to be contacted, and eventually publish a html report somewhere. These weeks I'm trying to collect my little spare time to setup a machine that would periodically build all ports in clc/contrib and log the results (see previous posts) in clc-devel. Drop me a mail if you'd like to contribute. (currently looking for good ideas to reduce processing time)
This is just an idea and I would propose to write it in python.
that's a must :-)
Cheers, Daniel
Regards, Simone Rota
On Thu, Oct 16, 2003 at 08:33:32AM +0200, Simone Rota <sip@varlock.com> wrote: Hi,
What do you mean by 'availability'? Would the script only check for availability of source() files, or try to build the port?
It just makes sure, that there will be no 404 error. It will not try to build the ports.
In both cases, I'd prefer not to add another tag to Pkgfile, I suggest an (independent) external list or something similar. Or, better again, the script could periodically check all ports and submit problems to the maintainers who want to be contacted, and eventually publish a html report somewhere.
This was also my second idea. I think it would be better in this way and so I'll do it.
These weeks I'm trying to collect my little spare time to setup a machine that would periodically build all ports in clc/contrib and log the results (see previous posts) in clc-devel. Drop me a mail if you'd like to contribute. (currently looking for good ideas to reduce processing time)
How can I contirbute? My spare time gets more and more less. :) Cheers, Daniel -- Daniel K. Gebhart http://informatik.uibk.ac.at/users/c703263/ Institute for Computer Science University of Innsbruck Fon: (office): +43 512 507 6490 Mail: <daniel.gebhart(at)uibk.ac.at>
On Thu, 16 Oct 2003 09:28:15 +0200 "Daniel K. Gebhart" <dkg@con-fuse.org> wrote: Hi Daniel,
What do you mean by 'availability'? Would the script only check for availability of source() files, or try to build the port?
It just makes sure, that there will be no 404 error. It will not try to build the ports.
got it. It's clear now.
In both cases, I'd prefer not to add another tag to Pkgfile, I suggest an (independent) external list or something similar. Or, better again, the script could periodically check all ports and submit problems to the maintainers who want to be contacted, and eventually publish a html report somewhere.
This was also my second idea. I think it would be better in this way and so I'll do it.
I'll add a third one (just to make thinks more complicated): if the script is developed as a tool mainly for maintainers, it could handle a filter param (ie: maintainer name or port path). This way a maintainer could be easily check only his/her ports. ie: # scriptname --maintainer=sip@varlock.com would check my ports; or: # scriptname --path=/usr/ports/custom Just an idea. Regards, Simone
On Wed, 15 Oct 2003, Daniel K. Gebhart wrote:
Hi,
Hi Daniel,
I know I'm new and should not be to loud. ;-) But I had a idea which I would like to propose. I hope you'll not catch it wrong..
The prt-check script I wanna write should check the availability of each port which has set the (new) tag "Check" to on and write warning mails to its maintainer if something goes wrong. So, the maintainer could decide if he/she gets warnings when something goes wrong with its port or not.
I'm not sure I really understand what you mean. And please give it another name. There's already a script called prtcheck in the prt-utils port.
This is just an idea and I would propose to write it in python.
Cheers, Daniel
Bye Martin
On Thu, Oct 16, 2003 at 08:45:24AM +0200, Martin Opel <martin.opel@informatik.fh-regensburg.de> wrote: Hi,
I'm not sure I really understand what you mean. And please give it another name. There's already a script called prtcheck in the prt-utils port.
What is unclear? Ok, the name is no problem. I can also call it portolize :) Its a mix between port, analyze and police. :) Cheers, Daniel -- Daniel K. Gebhart http://informatik.uibk.ac.at/users/c703263/ Institute for Computer Science University of Innsbruck Fon: (office): +43 512 507 6490 Mail: <daniel.gebhart(at)uibk.ac.at>
participants (3)
-
Daniel K. Gebhart -
Martin Opel -
Simone Rota