Ludovic Courtès transcribed 0.9K bytes:
> Hi ng0,
> 
> ng0 <ng0@infotropique.org> skribis:
> 
> > ng0 transcribed 1.7K bytes:
> >> Ludovic Courtès transcribed 0.2K bytes:
> >> > Hello,
> >> > 
> >> > Since nothing depends on lxqt-common, I suggest removing it.  We can
> >> > always revisit this decision later if needed.
> 
> [...]
> 
> > Okay, we still require it.
> > The last LXQT release is 0.11.1, and lxqt-session requires lxqt-common.
> 
> Are you sure?  lxqt-session in master does not depend on lxqt-common.

I am not working with master, I am working with what has been released,
ie the tarballs on download.lxqt.org or whatever the url was. This still
requires lxqt-common, and as I have no idea about the release cycle of
LXQT I would prefer to keep it (and to find a workaround for it not building).

> > lxqt-notificationsd 0.11.1 still depends on lxqt-common.
> > Probably some more packages depend on it, but more than 1 is already enough
> > for me NOT to kick it out.
> 
> lxqt-notificationsd is not in master though.

Sure, but I'm working on LXQT. Something not existing doesn't mean no one
is using it as a base to include packages depending on this… this is my way
to say: hey. I need this for stuff that seeks its way into Guix master for
another Desktop ;)

> In master, there are really zero packages depending on it, per “guix
> refresh -l”.
> 
> Currently lxqt-common does not build, due to the modified tarball.
> Could you figure out a way forward?

Okay, I did not know about the original issue. I will try, I'll report back.

> Thanks in advance!
> 
> Ludo’.
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.ng0.infotropique.org/dist/keys/
https://www.infotropique.org https://ng0.infotropique.org