Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #19157
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: [composer] duplicate vendor |
| Date | 2022-11-15 12:51 +0100 |
| Message-ID | <jthcphF5hp8U1@mid.individual.net> (permalink) |
| References | <tknt3k$1bj$2@gioia.aioe.org> <jtcbceFaq6aU1@mid.individual.net> <tkviks$be6$1@gioia.aioe.org> |
paul, 2022-11-15 09:29: > Il 13/11/22 14:56, Arno Welzel ha scritto: >> Composer is not intended to be used this way. Usually you have exactly >> *one* composer.json in your project and not multiple ones. > > A, B, and C would be three distinct projects (packages) IHMO, each with > their respective composer.json In that case your question makes no sense: "Can the directory *a* contains *vendor/test/c* be prevented?" If a, b and c are independent projects they won't influence each other. However if they are part of one single project then there must not be a "local" composer.json, because Composer is not intended to be used as a "local" package manager inside a package. -- Arno Welzel https://arnowelzel.de
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[composer] duplicate vendor paul <sk@i.p> - 2022-11-12 11:38 +0100
Re: [composer] duplicate vendor Arno Welzel <usenet@arnowelzel.de> - 2022-11-13 14:56 +0100
Re: [composer] duplicate vendor paul <sk@i.p> - 2022-11-15 09:29 +0100
Re: [composer] duplicate vendor Arno Welzel <usenet@arnowelzel.de> - 2022-11-15 12:51 +0100
Re: [composer] duplicate vendor paul <sk@i.p> - 2022-11-15 13:19 +0100
Re: [composer] duplicate vendor Arno Welzel <usenet@arnowelzel.de> - 2022-11-15 14:05 +0100
Re: [composer] duplicate vendor paul <sk@i.p> - 2022-11-15 15:30 +0100
Re: [composer] duplicate vendor paul <sk@i.p> - 2022-11-21 09:56 +0100
csiph-web