Namespacing introduced package duplication

[xire28]

There seems to be two naming conventions for components:

• The one used for dependencies without namespace :
  rails-assets-BOWER_PACKAGE_NAME
• The normal one with namespace :
  rails-assets-USERNAME--BOWER_PACKAGE_NAME

So if you add a package as a dependency and then add it on his own, will get two separated package for one repository:

Using a real example, I currently have the two following gems:

gem 'rails-assets-behavior-google-map-marker-ujs'
gem 'rails-assets-xire28--behavior-google-map-marker-ujs'

[jnylen]

@joshjordan and @hut8, wouldn't this kinda help #44 ?

[joshjordan]

@jnylen these are not forks - the two gems refer to the same repo.

@xire28 I see the issue, but do not understand the sequence of events that you believe caused it. Can you show me an example that will produce this state, or tell me the steps to reproduce with my own package?

[xire28]

Reproducting the issue is simple, you only need two packages (A and B) and have A be a dependency of B.

Then if you add the B package using rails-assets, the following gems are created:
rails-assets-USERNAME--B
rails-assets-A

After if you add the A package on his own, this gem is created:
rails-assets-USERNAME--A

In the end, you end up with three gems with a duplication for the package A:
rails-assets-USERNAME--B
rails-assets-USERNAME--A
rails-assets-A

[joshjordan]

That seems simple to address. Thanks!

On Thu, Apr 7, 2016 at 9:26 AM xire28 [email protected] wrote:

Reproducting the issue is simple, you only need two packages (A and B) and
have A be a dependency of B.

Then if you add the B package using rails-assets, the following gems are
created:
rails-assets-USERNAME--B
rails-assets-A

After if you add the A package on his own, this gem is created:
rails-assets-USERNAME--A

In the end, you end up with three gems with a duplication for the package
A:
rails-assets-USERNAME--B
rails-assets-USERNAME--A
rails-assets-A

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#318 (comment)