From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28823@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#28823: lxqt-common is deprecated
Date: Tue, 17 Oct 2017 12:26:58 +0000 [thread overview]
Message-ID: <20171017122658.d7jh5x3zrsg3j47j@abyayala> (raw)
In-Reply-To: <87wp3udyt8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-17 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 0:43 bug#28823: lxqt-common is deprecated Maxim Cournoyer
2017-10-14 16:10 ` Ludovic Courtès
2017-10-14 16:27 ` ng0
2017-10-15 19:37 ` Ludovic Courtès
2017-10-15 21:20 ` ng0
2017-10-16 7:29 ` Ludovic Courtès
2017-10-16 13:47 ` ng0
2017-10-16 17:48 ` ng0
2017-10-17 7:21 ` Ludovic Courtès
2017-10-17 12:26 ` ng0 [this message]
2017-10-22 16:55 ` ng0
2017-10-23 0:18 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171017122658.d7jh5x3zrsg3j47j@abyayala \
--to=ng0@infotropique.org \
--cc=28823@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).