I'm pretty sure this was a purposeful decision as a package is just a bunch of extensions. So now I'm curious, what's a use case for package media?

A bunch of extensions that share a media folder. Yes. I can put it inside a subpackage but the media is shared for all so the right would be to have the media outside.

I'm trying to think on an example:

We create a package that has:

• a component that shows twits in a page
• a module that shows twits in a module
• a plugin that injects twits in an article

All three extensions need the Twitter icon. And none of them should remove the Twitter icon if they are individually uninstalled.

For that specific case we will need this proposed feature.

(maybe is a silly example, I was trying to find something simple)

I'm definitely not against the idea, I just think of the package installer as basically being a trigger for multiple extensions so developers don't have to write that code themselves. Consistent behavior across all the adapters should be a goal, and something that we are doing in the JInstaller rewrite on the projects repo.
You may blame the J!Tracker Application for transmitting this comment.

Updated vs the latest master

I like this idea. Is there any chance that someone can post a package extension for testing?

@phproberto can you update this to staging please and if possible add a package for testing as per @betweenbrain request

@phproberto is this going to be updated or shall I close it?

I'll update it as soon I'm back from holidays but I'm closing it and reopen it when done.

Thanks for taking care

Make a note in your diary - and enjoy the rest of the holiday

On 2 January 2015 at 00:58, Roberto Segura notifications@github.com wrote:

I'll update it as soon I'm back from holidays but I'm closing it and
reopen it when done.

Thanks for taking care

—
Reply to this email directly or view it on GitHub
#1768 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/