From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28823@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#28823: lxqt-common is deprecated
Date: Sun, 15 Oct 2017 21:37:10 +0200 [thread overview]
Message-ID: <87d15ourrt.fsf@gnu.org> (raw)
In-Reply-To: <20171014162756.icdtyrmynjjwjoer@abyayala> (ng0@infotropique.org's message of "Sat, 14 Oct 2017 16:27:56 +0000")
ng0 <ng0@infotropique.org> skribis:
> Ludovic Courtès transcribed 0.8K bytes:
[...]
>> > Looking at the deprecated repo, it is not clear what needs to be
>> > done. Possibly the now deprecated lxqt-common has been broken up in
>> > various per-component repositories.
>>
>> Andreas, ng0: any idea?
>>
>> Thanks,
>> Ludo’.
>>
>
> So the Archlinux PKGBUILD uses:
> source=(
> "https://github.com/lxde/$pkgname/releases/download/$pkgver/$pkgname-$pkgver.tar.xz"
> "https://github.com/lxde/$pkgname/releases/download/$pkgver/$pkgname-$pkgver.tar.xz.asc"
> Gentoo uses:
> if [[ ${PV} = *9999* ]]; then
> inherit git-r3
> EGIT_REPO_URI="git://git.lxde.org/git/lxde/${PN}.git"
> else
> SRC_URI="https://downloads.lxqt.org/lxqt/${PV}/${P}.tar.xz"
> KEYWORDS="~amd64 ~arm ~arm64 ~x86"
> fi
>
> I seem to remember that for the lxqt I work on in one of my branches
> I used the lxqt.org domain.
Using tarballs from downloads.lxqt.org sounds like a good idea.
However, regardless of this, what’s up with the lxqt-common deprecation?
Is it replaced by something else? Should we just remove it?
I’m clueless about LXQt so any suggestions is welcome. :-)
Ludo’.
next prev parent reply other threads:[~2017-10-15 19:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d15ourrt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28823@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=ng0@infotropique.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.