At Fri, 10 Jul 2020 14:24:20 +0300, Denys Nykula wrote:
Subject: Re: pkgsrc build server
>
> "Greg A. Woods" 4 July 2020, 23:58:24:
>
> > # use pkgtools/autoswc to cache some autoconf results
> > #
> > .sinclude "/usr/pkg/share/autoswc/autoswc.mk&quo
"Greg A. Woods" 4 July 2020, 23:58:24:
> # use pkgtools/autoswc to cache some autoconf results
> #
> .sinclude "/usr/pkg/share/autoswc/autoswc.mk"
Hello, after your letter I went to look what autoswc is. Its Makefile
hardcodes CACHEDIR and MKCONF to root paths, /var/db/autoswc and
/etc/mk.conf.
On 04/07/2020 21:57, Greg A. Woods wrote:
At Sat, 4 Jul 2020 21:01:26 +0300, Dima Veselov
wrote:
Subject: Re: pkgsrc build server
What I want is to run "make install" on fast real production server
with lot of resources once and then have all of those packages built in
NFS DIST
rhia...@falu.nl (Rhialto) writes:
>> You can also use the pbulk system to build in a chroot. To
>Pkg_comp is I think a bit easier to set up than pbulk I think. Also you
>can "go into" the chroot interactively and poke around by hand, if
>packages don't build (which will happen of course).
On Sat 04 Jul 2020 at 19:53:45 -, Michael van Elst wrote:
> Building in a chroot is the most useful way, and it avoids
> conflicts with the (productive) host installation.
>
> You can look at the pkg_comp package that does exactly that.
That is what I do. There are pkg_comp1 and pkg_comp
mayur...@acm.org (Mayuresh) writes:
>On Sat, Jul 04, 2020 at 09:49:32PM -0400, Greg Troxel wrote:
>> >> I would say: don't ever use make update.
>> > Why does something exist that isn't to be used `ever'?
>> You seeme to have conflated "I would say" and "everyone woudl say".
>It's worthwhile to
Mayuresh writes:
> On Sat, Jul 04, 2020 at 09:49:32PM -0400, Greg Troxel wrote:
>> >> I would say: don't ever use make update.
>> > Why does something exist that isn't to be used `ever'?
>> You seeme to have conflated "I would say" and "everyone woudl say".
>
> It's worthwhile to explain why
On Sat, Jul 04, 2020 at 09:49:32PM -0400, Greg Troxel wrote:
> >> I would say: don't ever use make update.
> > Why does something exist that isn't to be used `ever'?
> You seeme to have conflated "I would say" and "everyone woudl say".
It's worthwhile to explain why even you'd say and my question
Mayuresh writes:
> On Sat, Jul 04, 2020 at 02:15:13PM -0400, Greg Troxel wrote:
>> I would say: don't ever use make update.
> Why does something exist that isn't to be used `ever'?
You seeme to have conflated "I would say" and "everyone woudl say".
>> Use pkg_rolling-replace if you need to.
>
On Sat, Jul 04, 2020 at 02:15:13PM -0400, Greg Troxel wrote:
> I would say: don't ever use make update.
Why does something exist that isn't to be used `ever'?
> Use pkg_rolling-replace if you need to.
Isn't replace a risky target in event of changes that require recursively
building what depends
At Sat, 4 Jul 2020 21:01:26 +0300, Dima Veselov
wrote:
Subject: Re: pkgsrc build server
>
> What I want is to run "make install" on fast real production server
> with lot of resources once and then have all of those packages built in
> NFS DISTDIR so any VM can just insta
kab...@lich.phys.spbu.ru (Dima Veselov) writes:
>Is there an opportunity to build a package with dependencies
>on production server without installing all dependencies?
>Maybe we can deploy NetBSD dist into a directory and build
>pkgsrc in chroot environment or there is more smooth
>way to do
On Sat, 4 Jul 2020 at 17:07, Dima Veselov wrote:
>
> Greetings,
> Is there an opportunity to build a package with dependencies
> on production server without installing all dependencies?
[This should belong to pkgsrc-users@]
I'd have thought it's not possible, however:
===>
04.07.2020 19:34, Greg Troxel wrote:
Is there an opportunity to build a package with dependencies
on production server without installing all dependencies?
Maybe we can deploy NetBSD dist into a directory and build
pkgsrc in chroot environment or there is more smooth
way to do that?
I don't
Dima Veselov writes:
> Good example I had started to concern was building SOGo (not built in
> pkgsrc releases) which also depend on LLVM/cLang 10 in pkgsrc-current,
> but only 9 is available in 2020Q1. I tried to build it on VM and this was
> quite a mistake - it took several days and about 5
On Sat, Jul 04, 2020 at 09:01:26PM +0300, Dima Veselov wrote:
> Sorry if my original question wasn't certain enough. There is no need to
> shrink building space. I can give unlimited space and lot of resources to
> build process, but I have it only on production servers and I don't want
> to mess
04.07.2020 19:51, Mayuresh пишет:
On Sat, Jul 04, 2020 at 07:07:02PM +0300, Dima Veselov wrote:
Is there an opportunity to build a package with dependencies
on production server without installing all dependencies?
Maybe we can deploy NetBSD dist into a directory and build
pkgsrc in chroot
On Sat, Jul 04, 2020 at 07:07:02PM +0300, Dima Veselov wrote:
> Is there an opportunity to build a package with dependencies
> on production server without installing all dependencies?
> Maybe we can deploy NetBSD dist into a directory and build
> pkgsrc in chroot environment or there is more
Dima Veselov writes:
> Sometimes we need to compile a package with lot of
> dependencies, let's say to use it on NetBSD VM. On one hand VM
> is limited in memory, CPU and especially disk space, on other
> hand we aren't rich enough to have separate server for pkgsrc
> builds.
a plausible
19 matches
Mail list logo
