Hi,
I'm the one Samuel talked to on the linked issue. I wanted to quickly
chime in to give the viewpoint of the polybar team and explain our
priorities on the sample config.
While I did express interest in auto-generating config files, this is
not a priority right now (and it likely won't be for a
Hello Antoine,
On Mon, 2 Mar 2020 at 20:13, Antoine Beaupré wrote:
> I tried the package available here:
>
> https://salsa.debian.org/debian/polybar
>
> It works well! One unfortunate problem I have found, however, is that it
> requires the siji font to work in its default configuration. That fon
On 2020-02-18 22:30:59, Samuel Henrique wrote:
> Control: owner -1 !
>
> On Mon, 27 Jan 2020 at 13:41, Jason Pleau wrote:
>>
>> I pushed what I had here: https://gitlab.com/jpleau/polybar/
>>
>> It's not targetting debian (simply because I'm using ubuntu these
>> days). Feel free to take whatever
Control: owner -1 !
On Mon, 27 Jan 2020 at 13:41, Jason Pleau wrote:
>
> I pushed what I had here: https://gitlab.com/jpleau/polybar/
>
> It's not targetting debian (simply because I'm using ubuntu these
> days). Feel free to take whatever you find useful
Thanks for that Jason, I pushed the curr
Hi, sorry for the delay.
On Sat, Jan 18, 2020 at 7:57 PM Samuel Henrique wrote:
>
> Hello Jason,
>
> > Feel free to take over the ITP and the packaging. I had deleted the
> > repo because I wanted to start over when I decided not to split the
> > libraries and I forgot to re-create and push what
Hello Jason,
> Feel free to take over the ITP and the packaging. I had deleted the
> repo because I wanted to start over when I decided not to split the
> libraries and I forgot to re-create and push what I had so far. I'll
> try to have it on salsa over the weekend.
Great, I managed to get a wor
Hi
On Sat, Jan 11, 2020 at 5:08 PM Samuel Henrique wrote:
>
> Hello Jason,
>
> I'm interested in having polybar packaged on Debian,
>
> I can see that you closed the ITP of the other two libs libxpp and i3ipcpp
> stating that they are no longer needed, and that the repository for polybar's
> pack
Hello Jason,
I'm interested in having polybar packaged on Debian,
I can see that you closed the ITP of the other two libs libxpp and i3ipcpp
stating that they are no longer needed, and that the repository for
polybar's
packaging on salsa is not available anymore.
Do you have update0s on its pack
Small update,
I pushed a change to i3ipcpp that also builds a shared library in
addition to the static library. (The i3ipcpp patches I will probably be
able to send upstream at some point). polybar correctly uses the shared
library, I think it's better this way.
I don't think I can do the same wi
Hi (again..!)
Didn't expect to get something to work so soon regarding the splitting
of the packages.
On salsa:
https://salsa.debian.org/jpleau-guest/polybar (BRANCH: split_pkg)
https://salsa.debian.org/jpleau-guest/libxpp
https://salsa.debian.org/jpleau-guest/i3ipcpp
In my sid chroot, all 3 no
Hi,
I'll try to answer your questions :)
On 03/28/2018 10:51 AM, Antoine Beaupré wrote:
> On 2018-03-27 21:15:35, Jason Pleau wrote:
>> Hi.
>>
>> I took a few hours last weekend to work on this.
>
> Awesome, thanks for the work!
>
>> While I was able to have "working" packages for both xpp and
On 2018-03-28 10:51:23, Antoine Beaupré wrote:
> Anyways, I guess that's an upstream problem as well, but it does seem
> like the default font provided in the example config file (Siji) is not
> in Debian, so that might be a nice addition. :)
For what it's worth, I managed to make polybar load the
On 2018-03-27 21:15:35, Jason Pleau wrote:
> Hi.
>
> I took a few hours last weekend to work on this.
Awesome, thanks for the work!
> While I was able to have "working" packages for both xpp and i3ipcpp,
> I could not get polybar to use them (the whole thing is glued together
> nicely it seems an
Hi.
I took a few hours last weekend to work on this. While I was able to
have "working" packages for both xpp and i3ipcpp, I could not get
polybar to use them (the whole thing is glued together nicely it seems
and trying to split them caused me headaches).
So I went ahead and worked on packaging
Hello.
On 02/24/2018 11:11 AM, Antoine Beaupré wrote:
> On 2018-02-23 22:47:08, Jason Pleau wrote:
>> Hi.
>> [...]
>> 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)
>
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...
>>
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
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...
.
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Jason Pleau
* Package name: polybar
Version : 3.0.4
Upstream Author : Michael Carlberg
* URL : https://github.com/jaagr/polybar/
* License : MIT/Expat
Programming Lang: C++
Description : fast and easy-to-use stat
19 matches
Mail list logo
