Florian, I love it, the tool itself is a break-through, just depends how we
use it properly.
On Mon, Jul 11, 2016 at 4:43 AM, pelzflorian (Florian Pelz) <
pelzflor...@pelzflorian.de> wrote:
> On 07/10/2016 08:43 PM, Bennett Piater wrote:
> > Thanks for your reply.
> > That would be the best you
On 07/10/2016 10:36 AM, arch-general-requ...@archlinux.org wrote:
> Send arch-general mailing list submissions to
> arch-general@archlinux.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.archlinux.org/listinfo/arch-general
> or, via email, send a
On 07/10/2016 08:43 PM, Bennett Piater wrote:
> Thanks for your reply.
> That would be the best you could do on the Arch side, but the problem is
> mostly that every upstream dev would need to maintain and keep his
> container up to date, isn't it? :)
>
pacpak is not meant to redistribute
On 07/10/2016 02:18 PM, pelzflorian (Florian Pelz) wrote:
> The intention is that, once implemented, `pacpak -Syu` or maybe `pacpak
> -Su` will install a current version of all apps and runtimes. Old
> versions of apps and app runtimes that are not used by any app could be
> cleaned by `pacpak
On 07/10/2016 03:22 PM, Mauro Santos via arch-general wrote:
> Personally I'd rather keep using the good old packages _but_ it would be
> nice to have an official tool to manage/run/create flatpak packages,
> this just to make sure that in case one needs to use a flatpak package
> nothing will
On 07/10/2016 04:45 PM, Levente Polyak wrote:
> We, as the Security Team, are strongly against any move to officially
> ship bundles that manage their dependency versions itself instead of
> regular software builds.
> […]
With pacpak, it will be the user’s responsibility to update the bundles
On 07/10/2016 11:05 AM, pelzflorian (Florian Pelz) wrote:
> [...] Bundles ship with the version
> of their dependencies which they need. Dependencies are not
> force-upgraded with the operating system, but easily upgradable by the
> bundle creator.
We, as the Security Team, are strongly against
On 07/10/16 at 01:59pm, LoneVVolf wrote:
> IF flatpak is to become supported on AL, i'd prefer pacman to handle it
> instead of a separate application.
flatpak is packaged in [extra], which for me means that it is indeed
supported.
>
> My personal preference though is for AL community to treat
On 10-07-2016 13:18, pelzflorian (Florian Pelz) wrote:
> Hello,
>
> On 07/10/2016 01:59 PM, LoneVVolf wrote:
>> My personal preference though is for AL community to treat flatpak
>> similar as derivative distros.
>>
>> something like : flatpak is unsupported on Arch linux, ask the flatpak
>>
Hello,
On 07/10/2016 12:52 PM, Bennett Piater wrote:
> Are you planning to address the catastrophy that ensues when 5000
> different versions of important libraries are installed at the same
> time, most of which will always be 5 critical security updates behind?
>
The intention is that, once
Hello,
On 07/10/2016 01:59 PM, LoneVVolf wrote:
> My personal preference though is for AL community to treat flatpak
> similar as derivative distros.
>
> something like : flatpak is unsupported on Arch linux, ask the flatpak
> creator(s) for help.
Hm… If there is not that much desire to support
IF flatpak is to become supported on AL, i'd prefer pacman to handle it
instead of a separate application.
My personal preference though is for AL community to treat flatpak
similar as derivative distros.
something like : flatpak is unsupported on Arch linux, ask the flatpak
creator(s) for
On Sun, Jul 10, 2016 at 12:52:04PM +0200, Bennett Piater wrote:
> I am very cynical about this container trend... :/
That's exactly the right attitude.
--
Tomasz Kramkowski | GPG: 40B037BA0A5B8680 | Web: https://the-tk.com/
> A specter is haunting the GNU/Linux ecosystem: the specter of per-user
> containerization. Software like Flatpak and Snappy promise fully
> sandboxed GNU/Linux application bundles (instead of merely launching an
> application with fewer privileges but without hiding the operating
> system, like
On Sun, 10 Jul 2016 10:01:38 +0200, Ralf Mardorf wrote:
>this doesn't restore speed dial.
Most likely it's possible to get back everything, but perhaps I didn't
notice all issues, perhaps I don't use some features.
The latest comments at
https://github.com/QupZilla/qupzilla/issues/2026 :
Hello,
A specter is haunting the GNU/Linux ecosystem: the specter of per-user
containerization. Software like Flatpak and Snappy promise fully
sandboxed GNU/Linux application bundles (instead of merely launching an
application with fewer privileges but without hiding the operating
system, like
On Sun, 2016-07-10 at 10:01 +0200, Ralf Mardorf wrote:
> $ mv .config/qupzilla/profiles/default/browsedata-backup(1).db
> .config/qupzilla/profiles/default/browsedata.db
$ mv .config/qupzilla/profiles/default/browsedata-backup\(1\).db
.config/qupzilla/profiles/default/browsedata.db
Hi,
to get back the history run
$ mv .config/qupzilla/profiles/default/browsedata-backup(1).db
.config/qupzilla/profiles/default/browsedata.db
but this doesn't restore speed dial. Perhaps it also does not restore
other data.
I opened an issue: https://github.com/QupZilla/qupzilla/issues/2026
18 matches
Mail list logo
