Add support for extensions that are in non-standard paths
Open, MediumPublic
Actions

Assigned To

None

Authored By

	siebrand
	Nov 22 2008, 2:06 PM

Description

ExtensionDistributor currently does not support downloading of extensions that are not on the root level. Two examples are 12 extensions in uniwiki/ and extensions in SocialProfile/

Details

Reference: bz16423

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:26 PM

• bzimport added a project: ExtensionDistributor.

• bzimport set Reference to bz16423.

• bzimport added a subscriber: Unknown Object (MLST).

siebrand created this task.Nov 22 2008, 2:06 PM

And the skins in extensions/skins

Bug 34484 has been marked as a duplicate of this bug. ***

Also need to add extensions inside extensions/examples.

Rephrasing bug summary.

Depending on how bug 37946 is implemented, this may become obsolete / naturally possible.

Are there any extensions in Git that don't have their own repo? I guess that is the equivalent problem under Git.

Addshore updated the task description. (Show Details)Dec 5 2015, 6:05 PM

Addshore set Security to None.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 5 2015, 6:05 PM

Meno25 unsubscribed.Feb 22 2016, 6:03 PM

In T18423#211534, @tstarling wrote:

Are there any extensions in Git that don't have their own repo? I guess that is the equivalent problem under Git.

There's a few, but they're the exception not the norm. Couple of fixes I can think of:

Provide a way to configure this in ExtDist. Seems kludgy though and and not future-proof
Break said extensions apart into their own repos. This is probably best practice anyway :)
Can extension.json or a similar manifest in the root specify "sub" extensions?

Krinkle unsubscribed.Aug 17 2017, 1:54 AM

Add support for extensions that are in non-standard pathsOpen, MediumPublicActions

Description

Details

Event Timeline

Add support for extensions that are in non-standard paths
Open, MediumPublic
Actions