Dependency on PEAR SDO ?????

In the dependencies section for 1.2.1 we list "PEAR
Package: sdo",
which links to something at http://pear.php.net/p
ackage/sdo - which
clearly doesn't exist.

Do we need to do a new release to remove this, or can it be
removed
independently (I'm ignorant of this process :-( ) ?

Graham.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On 4 Jun, 11:32, Graham Charters <gchart...googlemail.com> wrote:
> In the dependencies section for 1.2.1 we list
"PEAR Package: sdo",
> which links to something athttp://pear.php.net/
package/sdo- which
> clearly doesn't exist.
>
> Do we need to do a new release to remove this, or can
it be removed
> independently (I'm ignorant of this process :-( ) ?
>
> Graham.

It appears to be coming from the MakePackage.php script. the
line,

    $packagexml->addDependency('sdo', false, 'not',
'pkg');

I assume that because this is using the pear packager
technology it
goes ahead and makes the dependecy on PEAR automatically
rather than
PECL. Not sue how to fix this but on the other hand I don't
think we
need this line as it makes  it look like there is something
else that
the user has to go and download. It maybe that there is some
process
based reaon that this dependency line has to appear but I
don't know
what it is.

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

simonslawsgooglemail.com wrote:

> 
> On 4 Jun, 11:32, Graham Charters <gchart...googlemail.com> wrote:
>> In the dependencies section for 1.2.1 we list
"PEAR Package: sdo",
>> which links to something athttp://pear.php.net/
package/sdo- which
>> clearly doesn't exist.
> 
> It appears to be coming from the MakePackage.php
script. the line,
> 
>     $packagexml->addDependency('sdo', false, 'not',
'pkg');

This line came from the time of the package name change,
last November. 
I introduced it  to try to ensure that the SCA_SDO package
would not be 
installed alongside the SDO package, with resulting chaos.
If you RTFM 
(ht
tp://pear.php.net/reference/PEAR_PackageFileManager-0.1/PEAR
_PackageFileManager/PEAR_PackageFileManager.html) 
you'll see that its intent is to declare an incompatibility
between the 
two packages. It causes this entry in the <deps>
section of the package.xml:
   <dep type="pkg" rel="not"
optional="no">sdo</dep>

However if you look back through previous release
dependencies on the 
package page, you'll see that the confusing entry only
started to appear 
with release 1.1.2, in February, that is, not in 1.1.0 or
1.1.1 which 
had the same line in their MakePackage script.

I don't know what caused the behaviour to change, but since
we're still 
back at the V1 package file format, which is deprecated, we
can hardly 
complain. RTFM'ing again (a dangerous habit, I know) at 
http://pear.php.net/manu
al/en/developers.packagedef.php#guide.developers.packagedef.
deps, 
I note that rel="not" is only stated to work with
type="ext" or 
type="php". But we shouldn't use it to declare a
dependency on a certain 
level of the sdo extension, because the package installs the
extension 
(at least on *IX), and the chicken might not have been
present before 
the egg.

What I've done is check in a change to declare a conflict
dependency on 
the sdo_das_xml extension. This isn't a good test, because
the change of 
package name was not simultaneous with dropping sdo_das_xml
as a 
separate extension, but it may help sometimes. Mind you, we
won't know 
how this gets represented on the package page until either
we upload 
another release or someone reads the peclweb code to find
out .

What we should be doing is migrating to package file V2
format ...


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---