# RFC extensions_path directive

- Thread: https://externals.io/message/27764
- Original archive: https://news-web.php.net/php.internals/27764
- Started by Wez Furlong on 2007-02-04T19:12:07+00:00
- Messages: 5
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #27764 — Wez Furlong — 2007-02-04T19:12:07+00:00

URL: https://externals.io/message/27764#27764

We have a need for a search path for extensions, so that we can have  
a system provided set of extensions and an optional location for per- 
application extensions that either augment or override the baseline  
extensions.

To facilitate this, I propose that we create a new directive called  
extensions_path that allows the sysadmin to configure a search path  
for extensions.  I see the usage as going something like this:

extensions_path = "/local/extensions:$DEFAULT_EXTENSIONS_DIR"

Where $DEFAULT_EXTENSIONS_DIR evaluates to the default value of  
extensions_dir.
I think it's important to have a symbol for the default location, so  
that httpd.conf files don't have to have our API numbers encoded into  
them.

I don't mind if the actual symbol we use for the default manifests  
differently, so long as it works from within httpd.conf... if  
extensions_dir works there.  If it's php.ini only, I'm happy to use  
the existing constant expansion stuff we have for php.in... if that  
will work in a path string syntax.

I also don't mind if we simply expand extensions_dir to behave in  
this manner.

I just want to gather some feedback before writing some code.

To be super clear, I don't propose changing anything other than the  
searching behavior for extensions.

--Wez.

---

## #27765 — Marcus Boerger — 2007-02-04T19:45:44+00:00

URL: https://externals.io/message/27764#27765 · In reply to: #27764

Hello Wez,

  +1

marcus

Sunday, February 4, 2007, 8:12:07 PM, you wrote:

> We have a need for a search path for extensions, so that we can have  
> a system provided set of extensions and an optional location for per- 
> application extensions that either augment or override the baseline  
> extensions.

> To facilitate this, I propose that we create a new directive called  
> extensions_path that allows the sysadmin to configure a search path  
> for extensions.  I see the usage as going something like this:

> extensions_path = "/local/extensions:$DEFAULT_EXTENSIONS_DIR"

> Where $DEFAULT_EXTENSIONS_DIR evaluates to the default value of  
> extensions_dir.
> I think it's important to have a symbol for the default location, so  
> that httpd.conf files don't have to have our API numbers encoded into  
> them.

> I don't mind if the actual symbol we use for the default manifests  
> differently, so long as it works from within httpd.conf... if  
> extensions_dir works there.  If it's php.ini only, I'm happy to use  
> the existing constant expansion stuff we have for php.in... if that  
> will work in a path string syntax.

> I also don't mind if we simply expand extensions_dir to behave in  
> this manner.

> I just want to gather some feedback before writing some code.

> To be super clear, I don't propose changing anything other than the  
> searching behavior for extensions.

> --Wez.




Best regards,
 Marcus

---

## #27766 — Pierre — 2007-02-04T19:51:20+00:00

URL: https://externals.io/message/27764#27766 · In reply to: #27764

> extensions_path = "/local/extensions:$DEFAULT_EXTENSIONS_DIR"

+1

--Pierre

---

## #27779 — Sara Golemon — 2007-02-04T23:28:40+00:00

URL: https://externals.io/message/27764#27779 · In reply to: #27764

> To facilitate this, I propose that we create a new directive called 
> extensions_path that allows the sysadmin to configure a search path for 
> extensions.  I see the usage as going something like this:
> 
> extensions_path = "/local/extensions:$DEFAULT_EXTENSIONS_DIR"
> 
Seems very useful and a good tool for administrators to keep their 
installations organized.

+1, but I'd rather see extension_dir expanded than add a new option 
which does much the same thing.

-Sara

---

## #27790 — Brian Moon — 2007-02-05T07:25:16+00:00

URL: https://externals.io/message/27764#27790 · In reply to: #27779

+1 and a +1 on Sara's comment.  Especially if we are talking about PHP6. 
  I could see an argument for 5.x not getting this in extension_dir. 
But, I still think sticking with one setting is better.


Sara Golemon wrote:
> > […]
> Seems very useful and a good tool for administrators to keep their 
> installations organized.
> 
> +1, but I'd rather see extension_dir expanded than add a new option 
> which does much the same thing.
> 
> -Sara
> 

-- 

Brian Moon
-------------
http://dealnews.com/
It's good to be cheap =)