Re: Re: (Fwd) Re: How about adding "optional-cause" to pack
| From: | Greg Beaver | Date: | Sun, 09 May 2004 18:37:05 +0000 |
| Subject: | Re: Re: (Fwd) Re: How about adding "optional-cause" to pack | ||
| References: | 1 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-311@lists.php.net to get a copy of this message | ||
Hi Stefan,
Please hold off on moving too quickly with this, it will involve lots of changes to the installer, and we are in the process of implementing channels, which takes priority. I hate to squelch anything, but your patches won't work against the work I've been doing, causing lots more annoyance for you than is necessary.
I have slow internet here, I can send the work I'm doing tomorrow or a little later for a sample.
Greg
Stefan Neufeind wrote:
On 9 May 2004 at 11:25, Aidan Lister wrote:How would you do it, stefan? <deps> <dep type="php" rel="ge" version="4.3.0" reason="Needs file_get_contents to work" /> <dep type="pkg" rel="has" version="1.0" reason="Needs to be able to parse XML">XML_Parser</dep> </deps><deps> <dep type="php" rel="ge" version="4.3.0"><reason>Needs file_get_contents to work</reason></dep> <dep type="pkg" rel="has" version="1.0">XML_Parser<reason>Needs to be able to parse XML</reason></dep> </deps>I think the first example is the go, I don't like "cause", doesn't sound right.Yes, I think the first one (simply adding reason="..." as an attribute to the XML-tag) would be the easiest. Please note that it should be optional and should not be over-used (e.g. tons of info per dep). Mostly I was thinking about the optional dependencies, that give you an advice why it might be good to have them fulfilled. Like: <dep type="pkg" rel="ge" version="1.0.0" optional="yes" reason="strongly suggested for more accurate checks" />Package_A</dep> This would allow you to install the package, but be given an advice *why* it might be useful to also install the optional dependent package."Stefan Neufeind" <stefan@neufeind.net> wrote in message news:409CF274.30140.A1AE10@localhost...Now that there have been no objections on pear-dev and a few people even said that such an optional "reason"-attribute would be a nice thing in the deps to have, what do the people familiar with the installer / website-backend etc. think? Can it be implemented without a problem? Or might adding such an optional attribute break anything (e.g. the a bit outdated installers that people might still have running)? If nothing speaks against it, I'll write up a short enhancement proposal and list the necessary / useful changes. Stefan ------- Forwarded message follows -------package.xml?Date sent: Fri, 7 May 2004 23:03:06 -0400 From: Jon Parise <jon@php.net> To: pear-dev@lists.php.net Subject: Re: [PEAR-DEV] How about adding "optional-cause" toOn Thu, May 06, 2004 at 11:46:36PM +0200, Tobias Schlitt wrote:Hi Stefan Neufeind! You wrote:s/cause/reason "cause" is not the correct word for this kind of information. -- Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/) -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ------- End of forwarded message -------I was just thinking of what you think about possibly adding a field "optional-cause" to a dep in the package.xml. For optional dependencies this could be used to show the user "optional: packageABC; cause: needed for special func XYZ".I would preffer a general "cause" attribute for dependencies.