From nobody Mon Nov 20 03:59:20 2023 X-Original-To: freebsd-pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYYfv0cFCz51qkl for ; Mon, 20 Nov 2023 03:59:35 +0000 (UTC) (envelope-from reshadpatuck1@gmail.com) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYYft4Dnwz4TxN; Mon, 20 Nov 2023 03:59:34 +0000 (UTC) (envelope-from reshadpatuck1@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-40a48775c58so13641685e9.3; Sun, 19 Nov 2023 19:59:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700452772; x=1701057572; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MQV2sdZtUF8czY8K3Y3YgfSQCXAF4VTPXPYv8vifarU=; b=B9kE6DkbHQdjrHczlW8EawSXiEWPYIgVfwgdW0gms5xAYJ86aCMIZtyHHct6LS5+Oi Cn2/OIkEIALtZyAVmrtleIu7CZMm8jSjEj0Tp3hWfMN8hf37d49sM56crYBplQXmF1Tv pB7vrvM19swyxG0YE3tMyZgMy8vfAls+PvDGx+sZhyTTRGtLUSW6r/Qi2jNJDW1Tgeaj TGH0Gg5y60fqsiA6cn3iPgFlBq/riim+ZMQ3jyE3MARlg86hrkHHfP1AhoV60AJyZXuo euBqzoEAN/jX6dqnK0VQ1thnlzIrWkMHhXbLlpYs7C/v1y/nxQ7+EtQSix2/Sl4KXo5N cA6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700452772; x=1701057572; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MQV2sdZtUF8czY8K3Y3YgfSQCXAF4VTPXPYv8vifarU=; b=Afm9jinmlFMMXZ/JmVXbHFkJPahx8w4dGdZvV4iB9CYnEJ8ai78BC8psiskp3QT3xd REel1fs4wrU/2yfCYwKrPOUQTvtBZTtKeWy3bfAR6myGagvh7CcU2MZdpsZDXncokp6j OFC2NbGXSw5n6TnW0Ko5iR67VZV/WN9LRqy9ua30XfhRFvpcRbsBov1tD9/4p3K+xpwx XHSQ9TS8yM9wWSCxdzppgmxmpFEVVVWbHcjpaNRGeqhw0KVextoGtsmFc93A3YRJT9yr gINXHEv1fo4T4YqbJXl7FvlPBZTt+d97S3aPocPZQ6kEaKDWoPNzVOoeiU+7nafHjwCw 7org== X-Gm-Message-State: AOJu0Yy2AVfGtFYR9ZJVcKUwEyO228vsj2eEN1oj1myyy1uPAJQ7wAEv nS2taBGASNDca4nWq7pLiD73lofFSH5iSyy9GkZMhGj0dVI= X-Google-Smtp-Source: AGHT+IEFEhw268ekN+9YA5M+CnQkXo+LOOlzhghDgUWAADdTPUBoRWI50rlZ3rRSW4ag85JM4n/mDziN021LcjyuI+k= X-Received: by 2002:a05:600c:350a:b0:409:19a0:d247 with SMTP id h10-20020a05600c350a00b0040919a0d247mr5095002wmq.18.1700452771854; Sun, 19 Nov 2023 19:59:31 -0800 (PST) List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@freebsd.org MIME-Version: 1.0 References: <20231119191035.D7410A38FF@mail.toya.net.pl> In-Reply-To: From: Reshad Patuck Date: Mon, 20 Nov 2023 09:29:20 +0530 Message-ID: Subject: Re: Personal FreeBSD PkgBase Server To: vermaden Cc: freebsd-pkgbase@freebsd.org, bapt@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006c7d2a060a8d835c" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SYYft4Dnwz4TxN --0000000000006c7d2a060a8d835c Content-Type: text/plain; charset="UTF-8" Hi Vermaden, Once you build the packages from PkgBase (src repository) and your ports packages from poudriere, you can do one of the following. 1. Host both output directories as separate static web directories and configure pkg on your FreeBSD systems to reach out to two repositories (PkgBase and Poudriere) 2. Copy in the pkg files from both PkgBase and poudriere to a single directory and run the `pkg repo ${path-to-pkg-dir}` to create a unified repository and host that directory on a web server. This way you can have just one additional repository to configure. Best, Reshad On Mon, 20 Nov 2023 at 03:57, vermaden wrote: > Hi, > > it's good to see PkgBase seeing more light of day but my question is about > its build process. > > How to create the build process to create and host this PkgBase solution > on my own? > > I would like to create and maintain a custom FreeBSD kernel/base build and > then update it with PkgBase packages that I build with Poudriere. > > Can you share the instructions You use to create and maintain self PkgBase > solution? > > Thank You in advance. > > Regards, > vermaden > > --0000000000006c7d2a060a8d835c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Vermaden,

Once you build the pa= ckages from PkgBase (src repository) and your ports packages from poudriere= , you can do one of the following.
  1. Host both output direc= tories as separate=C2=A0static web directories and configure pkg on your Fr= eeBSD systems to reach out to two repositories (PkgBase and Poudriere)
    2. =
  2. Copy in the pkg files from both PkgBase and poudriere to a single direc= tory and run the `pkg repo ${path-to-pkg-dir}` to create a unified reposito= ry and host that directory on a web server. This way you can have just one = additional repository to configure.
Best,
Res= had

On Mon, 20 Nov 2023 at 03:57, vermaden <vermaden@interia.pl> wrote:
Hi,

it's good to see PkgBa= se seeing more light of day but my question is about its build process.

How to create the build pro= cess to create and host this PkgBase solution on my own?

I would like to create and maintain a custom FreeBSD kernel/base build and then update it with PkgBase packages that I build with Poudriere.
=

Can you share the instruction= s You use to create and maintain self PkgBase solution?

Thank You in advance.

Regards,
vermaden
=

--0000000000006c7d2a060a8d835c--