what are you thinking about the following features

[Beat Gätzi]

Hi,

olli hauer wrote:
> Hi,
> 
> what are you thinking about the following features.
> 
> For example you inject a big amount of ports to the build queue
> because you don't want to fiddle out all the depending ports or
> need the port even not only as dependency (list for ports build
> on a remote machine with 'pkg_info -qoa')
> 
> To make it more readable I will use addPort for the following statement.
> ./tc addBuildPortsQueueEntry -b ...
> 
> 
> addPort archivers/php5-zlib
> ...
> addPort databases/php5-pgsql
> addPort databases/postgresql84-client
> addPort databases/postgresql84-server
> ...
> addPort graphics/php5-gd
> addPort lang/php5
> ...
> addPort ports-mgmt/tinderbox
> ...
> addPort www/php5-session
> 
> 
> Now php5 is a dependency for php5-zlib but this port will build php5
> before, now tinderbox knows about both it build first php5 than
> php5-zlib and twenty ports later again php5.
> 
> Since tinderbox knows this is in the same build it could update the
> status off php5 to the last BuildDate and the status to 'SUCCESS' to
> prevent a second build.
> 
> Additional a small function like ./tc rebuildAllPorts which injects all
> finished ports back to the queue will become interesting since there are
> maybe now ports which have not updated but have an old decencies to
> php5-5.2.11 instead php5-5.2.12.
> 
> Nice will be also an additional button in the webui where you can reset
> a finished port back to the queue.

If you use tinderd there is already the possibility to reset a status of
a port in the queue. If you reset a finished port it will be build again.
Adding an additional button to the list_buildport view (or somewhere
else) may could confuse users which do not use tinderd.

Beat