[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#934948: Dropping dependencies to avoid extra binary package when same source package targets more than one environment



On Fri, 20 Dec 2019 22:29:33 +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote:
On Fri, 20 Dec 2019 00:01:01 +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote:
>  > * asking the maintainers of the Ruby libraries that ruby-task-list
> > recursively depends on (such as ruby-rack) to remove *their* > dependencies

Looking at ruby-rack now, it ships /usr/bin/rackup executable. So it looks like a new binary package rackup needs to be created in this case if I understood the decision correctly. Or can this be considered a non-userfacing executable? I don't know if any package use rack directly.

Fortunately, ruby-task-list dropped dependency on ruby-rack from version 2 and ruby-activesupport and ruby-nokogiri is only required for older versions of ruby. So we will just need to take care of ruby-html-pipeline and we can remove the other dependencies.


Reply to: