Modify ↓
Ticket #525 (closed defect: fixed)
pearpkg2: minimal version on dependency automatically set max and recommended
| Reported by: | Christian Weiske <cweiske@…> | Owned by: | victor |
|---|---|---|---|
| Priority: | low | Milestone: | 2.4.3 |
| Component: | phing-tasks-ext | Version: | devel |
| Keywords: | Cc: |
Description
When specifying only the minimum version of a dependency, I automatically get the maximal and recommended version set. This is semantically totally different, because I want people to simply update their packages.
Code:
<mapping name="deps">
<element>
<element key="channel" value="pear.php.net" />
<element key="name" value="HTML_QuickForm2" />
<element key="version" value="0.4.0" />
</element>
</mapping>
Result:
<package>
<name>HTML_QuickForm2</name>
<channel>pear.php.net</channel>
<min>0.4.0</min>
<max>0.4.0</max>
<recommended>0.4.0</recommended>
</package>
Solution: <min> and <recommended> should not be set automatically, only when specified explicitely.
Attachments
Change History
comment:1 Changed 18 months ago by victor
- Owner changed from mrook to victor
- Priority changed from major to trivial
- Status changed from new to assigned
comment:2 Changed 18 months ago by Christian Weiske <cweiske@…>
err. <max> and <recommended> should not be set automatically. Sorry.
Note: See
TracTickets for help on using
tickets.

You are right: "min", "max", and "recommended" are set to "version", if they are not explicitly specified. You advise not to auto-set "min" and "recommended", but auto-set "max" only?
Can you elaborate why current setting is semantically wrong?