On Sat, 20 May 2017 09:07:29 -0400,
Joseph Graham wrote:
> | /etc/makepkg.conf: line 148: /etc/libretools.d/librefetch-makepkg.conf:
> No such file or directory
Wait, what? makepkg.conf is edited to look for that file by the
libretools post-install script, and that file is part of libretools.
pacman-mirrorlist 20170503-1.parabola1 is out
oops! not until now do I realize I never released it from my staging
dir.
--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
___
Dev mailing list
Dev@lists.parabola.nu
On Tue, 23 May 2017 01:52:22 -0400,
Andreas Grapentin wrote:
> branches in git are meant for tracking variations of the same content,
> not different content entirely. directories are the right tool for that.
That's... not true. Branches are "meant" for tracking independent
trees. If the branch
On Tue, 23 May 2017 08:44:58 -0400,
fauno wrote:
> i agree, also the svn dir structure is awful,
Well, it's awful in git. But it actually works really well with svn's
idiosyncratic branching model.
Which is why Arch devs still use svn for their actual use, and their
svntogit is a "read only"
Andreas Grapentin writes:
> On Tue, May 23, 2017 at 02:34:59AM +0100, Josh Branning wrote:
>
> imo, if the data doesn't leave your system, regardless of what is being
> recorded, then this is really a non-issue. And if someone forces access
> to your system, enabling them
Megver83 wrote:
Isaac David wrote:
if so, I don't think you would gain much from
having many packages compile at the same time, given that all of
your
cores are already in use for the longest time.
But it is possible?
I think so, and you don't need a new libretools to achieve it imo.
Isaac David:
> yes, I can attest that compiling that many kernels every few weeks is
> pure madness and bad for your electricity bills :)
>
> do you have the -j MAKEFLAG equal the number of cores in your
> /etc/makepkg.conf?
Yes, I do.
$ cat /etc/makepkg.conf | grep MAKEFLAG
#MAKEFLAGS="-j2"
Luke Shumaker:
What do you guys think
about splitting abslibre.it so that each package is on its own branch,
instead of having all of them side-by-side on the same branch? There
would be no 'master' branch.
out of curiosity, what are the perceived advantages?
--
Isaac David
GPG:
yes, I can attest that compiling that many kernels every few weeks is
pure madness and bad for your electricity bills :)
do you have the -j MAKEFLAG equal the number of cores in your
/etc/makepkg.conf? if so, I don't think you would gain much from
having many packages compile at the same time,
I agree, I think that each branch should have its -testing, -multilib
and -multilib-testing directories too. For example, the abslibre.git
libre branch should have the libre, libre-testing, libre-multilib and
libre-multilib-testing directories. I liked the idea, and we could also
deprecate the
Hi, as a package maintainer, I was thinking on why libremakepkg can't
compile multiple packages at the same time, because for me, as a
maintainer of some kernels, it would be much more efficient and fast if
I could do that. What I do is to compile with 2 different machines (one
is x86 and the
Andreas Grapentin writes:
> On Mon, May 22, 2017 at 09:19:41PM -0400, Luke Shumaker wrote:
>> Without making any concrete decisions yet: What do you guys think
>> about splitting abslibre.it so that each package is on its own branch,
>> instead of having all of them
andr...@grapentin.org wants to notify you that the following packages may be
out-of-date:
* cups-filters 1.13.5-1.parabola1 [libre] (i686):
https://parabolagnulinux.org/packages/libre/i686/cups-filters/
* cups-filters 1.13.5-1.parabola1 [libre] (x86_64):
13 matches
Mail list logo