Re: [Bsdrp-devel] package-recursive

[Emre G. <em...@gu...>]

On 09/29/2014 03:40 PM, Olivier Cochard-Labbé wrote:
> 
> On Sun, Sep 28, 2014 at 11:06 PM, Emre Gundogan <em...@gu...
> <mailto:em...@gu...>> wrote:
> 
>     Is there any reason why 'package-recursive' target is not used to
>     automatically generate port dependencies in the 'add_port' command?
>     Since this approach may introduce a number of ports that are not
>     necessary for run-time system, those could then be removed by 'pkg
>     autoremove' in the 'cleanup_ports' function... I tested it a few times
>     with something like 'databases/rrdtool' that has a notoriously long
>     dependency list. It seems to work, although I have no idea if
>     'package-recursive' could be relied upon for all the ports that are out
>     there. For instance, 'security/bro' has an optional dependency
>     'ftp/curl', which is normally pulled in during buildworld. But when disk
>     image is generated, 'ftp/curl' is not added automatically (needs a
>     redundant add_port "ftp/curl"). There is a comment in the nano file
>     referring to a broken system, but I don't know if it still applies to
>     the FreeBSD 10 release cycle.
> 
> 
> Yes it seems still broken:
> 
> I've just did a small test:
> 1. Replaced the "install package" py "install package-recursive"
> 2. Commented all manually-declared running-deps for net/quagga (this
> mean: devel/libdlmalloc, print/indexinfo, security/libgpg-error,
> security/libgcrypt)
> 3. Started a build (on a FreeBSD-10.1-BETA3)
> … and the result are still bad because at the end, we should have found
> all theses commented running-deps packages in the folder
> /usr/obj/BSDRP.amd64/ports/packages/All/… Buth they aren't.
> 
> Regarding nanobsd evolution:
> I'm just back from the EuroBSDCon, and I've speak with ba...@fr...
> <mailto:ba...@fr...> that propose me an idea for a next-gen nanobsd.
> The idea is simple: Just adding "nanobsd" as target mode to poudriere
> (https://www.freebsd.org/doc/handbook/ports-poudriere.html).
> - The final image will still be 100% compliant with nanobsd image
> partition scheme
> - All this dependency and useless packages will be managed by poudriere
> - It will add the cross-compilation feature too
> 
> Regards,
> 
> Olivier

Hi Olivier,
Thanks a lot for the heads-up on nanobsd-poudriere plans, it sounds
great. By the way, I did exactly like you describe eliminating all the
manual dependencies for quagga, and I had all the run-depends libs in
the packages/All (except libdlmalloc, as my config had only
"WITH\="ISISD OSPF_OPAQUE_LSA TCPSOCKETS\""). Don't remember why I
excluded dlmalloc, maybe I ran into a problem... Anyway, I suspected
that package-recursive might still be broken. Thanks again for
confirming that.

Regards,
Emre.