On 07/11/2016 10:40 PM, ITwrx.org wrote:
> Florian,
>
> thanks for the reply and link. Well behaved build systems and/or the
> link you sent is what i alluded to with my "cooperation from upstream"
> comment. It seems to me, upstream and distros should get together and
> agree on a set of standard
On 07/12/2016 09:29 AM, Chao Feng via arch-general wrote:
> Florian,
>
> What is the target user of pacpak? Arch users or App developers?
>
> I think Flatpak and Arch rolling release model mainly fix the same issue:
> Shipping cutting edge softwares quickly and stay close with upstream.
>
> Arc
On Monday 11 July 2016 18:57:38 pelzflorian wrote:
> On 07/11/2016 05:01 PM, Maxwell Anselm via arch-general wrote:
> > I think the tool is great Florian, but I do not think that it warrants
> > official support. Consider examples like pacgem or pip2pkgbuild. These
> > tools help integrate Ruby/Pyt
No worries, we all have competing priorities.
Ok, thanks for the info, and for looking into the update.
On 07/11/2016 01:00 AM, arch-general-requ...@archlinux.org wrote:
> On 07/11/2016 01:09 AM, Information Technology Works wrote:
>> > Aren't snaps, flatpak and appimage missing the boat in a concerning
>> > way? Shouldn't the Gnu+Linux ecosystem be focusing on automating the
>> > package building/m
On 07/11/2016 06:14 PM, G. Schlisio wrote:
> […]
> an install command would likely look like -S like in pacman?
> whats the base for installation? PKGBUILDs (from AUR/ABS), official
> repos, some new platform containing build recipes for pacpak?
>
pacpak will use the official repos (or other repos
On 07/11/2016 05:01 PM, Maxwell Anselm via arch-general wrote:
> I think the tool is great Florian, but I do not think that it warrants
> official support. Consider examples like pacgem or pip2pkgbuild. These
> tools help integrate Ruby/Python packages (which are usually managed via a
> separate pa
> `pacpak -Syu` would therefore always install exactly the same version of
> the software as available with regular pacman.
-Syu with pacman means refresh databases and install all available
updates. does this mean pacpak execute this logic on all installed
containers as pacman executes on all ins
On 07/10/2016 10:43 PM, pelzflorian (Florian Pelz) wrote:
> pacpak is not meant to redistribute already packaged containers from
> upstream. Instead it can be used to create containers from existing Arch
> packages. Basically, a copy of Arch is installed into a container
> runtime. Then different
I think the tool is great Florian, but I do not think that it warrants
official support. Consider examples like pacgem or pip2pkgbuild. These
tools help integrate Ruby/Python packages (which are usually managed via a
separate package manager) into pacman. They are great for users who want
pacman to
Hi,
no there is no issue. I just have little free time to do the update. I will
try to do it this or next week.
Update will come, sorry for a little delay on this topic.
Cheers
Daniel
Phil Uithoven schrieb am Sa., 9. Juli 2016, 14:16:
>
> Is there an issue with updating the mono package?
>
> T
11 matches
Mail list logo
