Files
poky/bitbake/lib/toaster/toastergui/templates/package_built_dependencies.html
Dave Lerner 14a84434a1 bitbake: toaster: show installed package name
[YOCTO #5922]

Implement changes that show the installed package name after the
official 'recipe-named' package name.  If the alias exists and
is different than the package name, then the alias is shown as a
'muted' string after the package name in the form 'as some-alias-name'.
This formatting appears in the included package pages in the elements:
* local breadcrumbs at the top of package included pages,
* <h1> title headings along with a help bubble that is not hovering,
and
* package lists where the help bubble appears when the mouse hovers
over the row.

The changes in detail in this patch per file are:
views.py
- added function that tests whether the package object's installed_name
should be shown,
- added function that appends package name with version and revision to
encapsulate package name formatting in one place and referred to as
package.fullpackagespec,
- changed package_built* and package_included* functions to use both
of the above new formatting functions, passing the formatted values to
templates, and
- adhered to django coding styles by renaming  module local
'get_package*' functions with "_" prefix.

package_detail_base.html
- added display of package aliases for included package page,
- refactored to use package.fullpackagespec, formatted by view function,
- added javascript function to format package alias with help, and
- removed trailing whitespace.

package_included_detail.html
- used javascript function above to format package alias, and
- refactored to use package.fullpackagespec.

package_included_dependencies.html
- used javascript function above to format package alias,
- refactored to use package.fullpackagespec,
- forced empty data cells following hover-help to draw borders
by appending space, and
- removed trailing whitespace.

package_included_reverse_dependencies.html
- use javascript function above to format package alias,
- refactor to use views fullpackagespe, and
- force empty data cells following hover-help to draw borders
by appending space.

package_built_detail.html
- refactored to use package.fullpackagespec, and
- removed trailing whitespace.

package_built_dependencies.html
- refactored to use package.fullpackagespec, and
- removed trailing whitespace.

projecttags.py
- removed unused filter to handle installed name
- removed extra spaces around "title = " in format_vpackage_namehelp

(Bitbake rev: c604e14df8cdb1f47535f093d7044955d4c2057d)

Signed-off-by: Dave Lerner <dave.lerner@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-28 13:44:52 +00:00

109 lines
5.3 KiB
HTML

{% extends "package_detail_base.html" %}
{% load projecttags %}
{% block tabcontent %}
<ul class="nav nav-pills">
<li class="">
<a href="{% url 'package_built_detail' build.id package.id %}">
<i class="icon-question-sign get-help" data-toggle="tooltip" title="Shows the files produced by this package."></i>
Generated files ({{package.buildfilelist_package.count}})
</a>
</li>
<li class="active">
<a href="{% url 'package_built_dependencies' build.id package.id %}">
<i class="icon-question-sign get-help" data-toggle="tooltip" title="Shows the runtime packages required by this package."></i>
Runtime dependencies ({{dependency_count}})
</a>
</li>
</ul>
<div class="tab-content">
<div class="tab-pane active" id="dependencies">
{% ifequal runtime_deps|length 0 %}
<div class="alert alert-info">
<strong>{{package.fullpackagespec}}</strong> has no runtime dependencies.
</div>
{% else %}
<div class="alert alert-info">
<strong>{{package.fullpackagespec}}</strong> is <strong>not included</strong> in any image. These are its projected runtime dependencies if you were to include it in future builds.
</div>
<table class="table table-bordered table-hover">
<thead>
<tr>
<th>Package</th>
<th>Version</th>
<th>Size</th>
</tr>
</thead>
<tbody>
{% for runtime_dep in runtime_deps %}
{% ifequal runtime_dep.version '' %}
<tr class="muted">
<td>{{runtime_dep.name}}</td>
<td>{{runtime_dep.version}}</td>
<td></td>
</div>
</tr>
{% else %}
<tr>
<td>
<a href="{% url 'package_built_detail' build.id runtime_dep.depends_on_id %}">
{{runtime_dep.name}}
</a>
</td>
<td>{{runtime_dep.version}}</td>
<td>{{runtime_dep.size|filtered_filesizeformat}}</td>
</tr>
{% endifequal %}
{% endfor %}
</tbody>
</table>
{% endifequal %}
{% ifnotequal other_deps|length 0 %}
<h3>Other runtime relationships</h3>
<table class="table table-bordered table-hover">
<thead>
<tr>
<th>Package</th>
<th>Version</th>
<th>Size</th>
<th>
<i class="icon-question-sign get-help" title="There are 5 relationship types: recommends, suggests, provides, replaces and conflicts"></i>
Relationship type
</th>
</tr>
</thead>
<tbody>
{% for other_dep in other_deps %}
{% ifequal other_dep.version '' %}
<tr class="muted">
<td>{{other_dep.name}}</td>
<td>{{other_dep.version}}</td>
<td></td>
<td>
{{other_dep.dep_type_display}}
<i class="icon-question-sign get-help hover-help" title="{{other_dep.dep_type_help}}" ></i>
</td>
</tr>
{% else %}
<tr>
<td>
<a href="{% url 'package_built_detail' build.id other_dep.depends_on_id %}">
{{other_dep.name}}
</a>
</td>
<td>{{other_dep.version}}</td>
<td>{{other_dep.size|filtered_filesizeformat}}</td>
<td>
{{other_dep.dep_type_display}}
<i class="icon-question-sign get-help hover-help" title="{{other_dep.dep_type_help}}" ></i>
</td>
</tr>
{% endifequal %}
{% endfor %}
</tbody>
</table>
{% endifnotequal %}
</div> <!-- tab-pane -->
</div> <!-- tab-content -->
{% endblock tabcontent %}