Re: Mbld: Open Questions.

[Daniel Cegiełka <daniel.cegielka@xxxxxxxxx>]

2014-12-15 0:10 GMT+01:00 Ori Bernstein <ori@xxxxxxxxxxxxxx>:
> On Sun, 14 Dec 2014 12:58:07 +0100
> Daniel Cegiełka <daniel.cegielka@xxxxxxxxx> wrote:
>
>> 2014-12-14 6:06 GMT+01:00 Ori Bernstein <ori@xxxxxxxxxxxxxx>:
>>
>> > configure scripts
>
> Nothing on this?
>

>configure scripts

>   With the 'make' based systems, I would ship with a configure script
>    that handled things like, eg, figuring out which prefix to install
>    programs to, which assembler to use, and so on.

getenv("MYRHOME")?

>    With mbld, I currently support command line flags for the prefix
>    and the destdir, but these are not available to the source code
>    in any way, and I'm not sure if they should be, or how.

yes, this is a small problem, but you can always generate
env.myr/conf.myr etc. on the fly (from mbld).

>    I really want to avoid something like autoconf, and library probing
>    should be a solvedish issue regardless. Still, I feel like I may end
>    up running into some issues here if I don't try something.

Autoconf is definitely a bad idea. We do not have fragmentation (eg.
libs versioning), so autoconf is a sophisticated solution to a
nonexistent problem (in myrddin).

>    How do we want to handle this? Should we still be relying on system
>    probing shell scripts? (ugh)? Is there any better option that we
>    should be looking at?

eg. as a mbld's option. Plan9 way:

objtype=arch mk install

> I was wondering if there was a sane way of doing somthing like
>
>     mbld -p deb,rpm,...
>
> I don't think there are, though.

This is a task for the distros maintainers :)