Skip to content
This repository has been archived by the owner on Aug 6, 2023. It is now read-only.

\PEAR2\Pyrus\Package exception #30

Closed
cweiske opened this issue Jun 3, 2011 · 5 comments
Closed

\PEAR2\Pyrus\Package exception #30

cweiske opened this issue Jun 3, 2011 · 5 comments
Labels
Milestone

Comments

@cweiske
Copy link
Contributor

cweiske commented Jun 3, 2011

Description:

When creating a new instance of a package that is all ready in the rgistry a exception occures.

Test script:

fromString('pear2.php.net/P...') #1 D:\pear\repo\php\PEAR2\Pyrus\Package.php(55): PEAR2\Pyrus\Package\Remote->__construct('pear2.php.net/P...', Object(PEAR2\Pyrus\Package)) #2 D:\pear\packages\PackageManager\tests\u.php(7): PEAR2\Pyrus\Package->__construct('pear2.php.net/P...') #3 {main} thrown in D:\pear\repo\php\PEAR2\Pyrus\Package\Remote.php on line 282
@cweiske
Copy link
Contributor Author

cweiske commented Jun 3, 2011

saltybeagle (Brett Bieber)
Hmm, I think in this case the exception is to be expected.

To retrieve information about remote packages, pass $forceremote = true to Package::__construct so it won't look at the local registry before comparing against remote packages.

@cweiske
Copy link
Contributor Author

cweiske commented Jun 3, 2011

boekkooi (Warnar Boekkooi)
Okee so what your saying is don't use Package for getting information about a package that's allready installed? but use Registry::package and Registry::exists?

@fpoirotte
Copy link
Member

Does this mean this ticket is bogus then?

@till
Copy link
Member

till commented Nov 5, 2012

@cweiske Ping. Close it, if it's bogus.

@cweiske
Copy link
Contributor Author

cweiske commented Nov 6, 2012

I don't really like the current behavior, but ok. There is an alternative we can use.

@cweiske cweiske closed this as completed Nov 6, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants