public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] Contribute many ebuilds at once
  @ 2002-06-10  0:50 99% ` Justin Lambert
  0 siblings, 0 replies; 1+ results
From: Justin Lambert @ 2002-06-10  0:50 UTC (permalink / raw
  To: gentoo-dev

On Sunday 09 June 2002 10:39 am, Karl Trygve Kalleberg wrote:

> Increasing the visibility of which ebuild submissions are in the pipe is
> something we'd very much like to do. It is a fairly easy affair, and will
> probably be handled in my proposition for a new ebuild submission system.

I haven't really developed the idea sitting around in my head yet but trying 
to piece all of the ideas floating around for an interface (note: i am not an 
interface design person so this could be way wrong).  Would it make sense to 
have maybe a heirarchial view for submitted ebuilds for where their creator? 
thinks they should go in the portage tree.  Maybe on the views have different 
icons showing which tree has new ebuilds that need testing and it would be 
easier for people that only like to test, for example, chat programs (assume 
there are these people) to focus on their area of expertise.  I don't know if 
the new ebuild submission thing will be something that will help this problem 
or not.  I also could be way out in left field.

> The biggest problem for the maintainers is the varying quality of ebuilds.
> Few, if any submissions are correct on the first go, and many of the
> bugs/problems identified could be checked programmatically.
>
> Submissions should then be run through a "screening" script that checks
> for syntactic and semantic completeness, verifies dependencies,
> well-formedness of ebuild, digest, changelog, etc.

It wouldn't be very hard to write a recursive descent parser to run through an 
ebuild would it?  I can try to whip something out myself if needed or work 
with someone to write possibly a perl script that can be run on the files 
after an ebuild is submitted, before the confirmation page saying that they 
tested the layout and formality requirements.  The biggest problems I'd have 
with this is that I know a very little bit of python and don't have a whole 
lot of experience with complex ebuilds.  I don't think it would be super hard 
with basic ones though.  Let me know if this is something that is of use and 
someone would like to help me with it.


Justin Lambert



^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2002-06-09 15:39     [gentoo-dev] Contribute many ebuilds at once Karl Trygve Kalleberg
2002-06-10  0:50 99% ` Justin Lambert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox