Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Dmitry Smirnov
On Wednesday, 27 April 2016 7:20:54 PM AEST Balasankar C wrote: > It is a balance between following standards and common sense. If the > package is used mainly as a library, name it ruby-foo. If it is mainly > used as an application, name it foo. Outliers, as always, will occur - but > in negligibl

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Balasankar C
On 27 April 2016 6:16:56 pm IST, Antonio Terceiro wrote: > >by your line of thinking we would be splitting every single application >in 2 packages (foo and ruby-foo, foo and python-foo, foo and >libfoo-perl), because every reasonably engineered application has >library code. > >That does not seem

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Antonio Terceiro
On Wed, Apr 27, 2016 at 10:02:30PM +1000, Dmitry Smirnov wrote: > On Wednesday, 27 April 2016 8:32:06 AM AEST Antonio Terceiro wrote: > > I can point you to countless examples of applications written Perl and > > Python whose libraries can be loaded from the global namespace, or Perl > > and Python

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Dmitry Smirnov
On Wednesday, 27 April 2016 8:32:06 AM AEST Antonio Terceiro wrote: > I can point you to countless examples of applications written Perl and > Python whose libraries can be loaded from the global namespace, or Perl > and Python libraries that also provide executables. I think it is not about excep

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Antonio Terceiro
On Wed, Apr 27, 2016 at 08:32:18PM +1000, Dmitry Smirnov wrote: > On Tuesday, 26 April 2016 11:31:45 AM AEST Antonio Terceiro wrote: > > On Tue, Apr 26, 2016 at 08:24:39AM +1000, Dmitry Smirnov wrote: > > > It is true that for now there are no packages depending on "ruby-ghi". > > > But eventually

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Dmitry Smirnov
On Tuesday, 26 April 2016 11:32:21 AM AEST Antonio Terceiro wrote: > On Tue, Apr 26, 2016 at 08:24:39AM +1000, Dmitry Smirnov wrote: > > On Monday, 25 April 2016 4:37:56 PM AEST Hleb Valoshka wrote: > > > If ghi is the only consumer of ruby-ghi then I don't see any reason to > > > introduce a new p

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-27 Thread Dmitry Smirnov
On Tuesday, 26 April 2016 11:31:45 AM AEST Antonio Terceiro wrote: > On Tue, Apr 26, 2016 at 08:24:39AM +1000, Dmitry Smirnov wrote: > > It is true that for now there are no packages depending on "ruby-ghi". > > But eventually there are may be some packages that need it. Since library > > is expose

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-26 Thread Antonio Terceiro
On Tue, Apr 26, 2016 at 08:24:39AM +1000, Dmitry Smirnov wrote: > On Monday, 25 April 2016 4:37:56 PM AEST Hleb Valoshka wrote: > > If ghi is the only consumer of ruby-ghi then I don't see any reason to > > introduce a new package. So I suggest to merge. > > Thank you, I'll consider merging. > >

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-26 Thread Antonio Terceiro
On Tue, Apr 26, 2016 at 08:24:39AM +1000, Dmitry Smirnov wrote: > On Monday, 25 April 2016 4:37:56 PM AEST Hleb Valoshka wrote: > > If ghi is the only consumer of ruby-ghi then I don't see any reason to > > introduce a new package. So I suggest to merge. > > Thank you, I'll consider merging. plea

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-25 Thread Dmitry Smirnov
On Monday, 25 April 2016 4:37:56 PM AEST Hleb Valoshka wrote: > If ghi is the only consumer of ruby-ghi then I don't see any reason to > introduce a new package. So I suggest to merge. Thank you, I'll consider merging. It is true that for now there are no packages depending on "ruby-ghi". But eve

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-25 Thread Hleb Valoshka
On 4/25/16, Dmitry Smirnov wrote: >> 1) upstream is not merged to master > > Intentional. See gbp.conf. Okay, but it's not a layout used by ruby-pkg-extras team afaik. >> 2) as ghi is an application not a library I consider to rename the >> package to just ghi > > Sorry, I don't quite follow yo

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-25 Thread Dmitry Smirnov
Thank you for your feedback, Hleb. On Monday, 25 April 2016 2:19:47 PM AEST Hleb Valoshka wrote: > 1) upstream is not merged to master Intentional. See gbp.conf. > 2) as ghi is an application not a library I consider to rename the > package to just ghi Sorry, I don't quite follow you... There

Re: ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-25 Thread Hleb Valoshka
On 4/25/16, Dmitry Smirnov wrote: > Since I'm not very experienced in packaging Ruby apps may I ask for quick > review of my work please? Package repository can be found here: > >https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-ghi.git 1) upstream is not merged to master 2) as ghi is an a

ghi: please review (new package, CLI interface to GitHub issue tracker)

2016-04-25 Thread Dmitry Smirnov
Dear Team, I'm working on packaging new "ghi" package [1] (CLI interface to GitHub issue tracker). Since I'm not very experienced in packaging Ruby apps may I ask for quick review of my work please? Package repository can be found here: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-g