On 2018-02-23 22:47:08, Jason Pleau wrote:
> Hi.
>
> On 02/20/2018 01:51 PM, Antoine Beaupre wrote:
>> On Sat, Feb 25, 2017 at 10:48:12PM -0500, Jason Pleau wrote:
>>> I plan to maintain this package in collab-maint on alioth
>>
>> Any progress here? I'm interested in tryint that stuff out...
>>
>> .
>>
>
> I originally replied on IRC but I'll go into more details here :
>
> There are a few missing packages in Debian before I can start working on
> polybar itself:
>
> When we look at the lib/ folder there are these libraries that aren't in
> the archive:
>
> i3ipcpp (github.com/jaagr/i3ipcpp, forked from drmgc/i3pcpp)
> - auss (github.com/jaagr/auss, forked from drmgc/auss)
> - jsoncpp (seems to be in Debian as src:libjsoncpp)
> xpp (github.com/jaagr/xpp, forked from jotrk/xpp)
>
>
> I don't mind doing the work of packaging these 3 libraries, however I
> would package the forks, unless someone wants to step in and try to get
> the forks merged into their original upstreams.
Makes sense. Should we file RFPs for those or will you Just Do It? :)
> There are also two headers included
> - concurrentqueue/include/moodycamel/blockingconcurrentqueue.h
> - concurrentqueue/include/moodycamel/concurrentqueue.h
>
> These headers seem to be included in two other projects (radmap and
> salmon). Is it ok to also include these directly with polybar ?
I would assume so, unless the code is identical and there is a
meaningful way to factor those out in the long term (e.g. get all the
upstreams to agree to move those to a library).
If there's already code duplication at that level, I'd say ignore this
for now.
> I'll try to get started on this soon, it's been a year since I filed the
> ITP and I am still using polybar from a manual build / install..
That would be great.
> Of course, I would welcome any help with this.
I don't have much time, but I would gladly test packages and I can
sponsor/review uploads.
A.
--
The desire to sacrifice an entire lifetime to the noblest of ideals
serves no purpose if one works alone.
- Che Guevara
