<div><br><div class="gmail_quote"><div dir="auto">On Fri, Dec 1, 2017 at 1:22 PM Matthew McClintock <<a href="mailto:msm-oss@mcclintock.net">msm-oss@mcclintock.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Dec 1, 2017 at 2:13 PM, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
> On Fri, Dec 1, 2017 at 11:30 AM, Andre McCurdy <<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>> wrote:<br>
>> On Fri, Dec 1, 2017 at 3:07 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>> wrote:<br>
>>> Extend lnr to have a --force option?<br>
>><br>
>> Is there ever a case where we want lnr to fail if the target already exists?<br>
>><br>
>> There are plenty of existing examples in oe-core where rm is run<br>
>> before lnr (and in the cases where it's not, it's perhaps just a bug<br>
>> or an oversight).<br>
>><br>
>> So I think either leave the v1 patch as-is and run rm before lnr in<br>
>> musl do_install as we already do elsewhere, or update lnr so that it<br>
>> unconditionally removes any pre-existing target?<br>
><br>
> I like Ross'es suggestion to modify lnr implementation as an<br>
> independent patch and<br>
> rebase your patch on top. Maybe a cleanup later to remove all rm cmds<br>
> that are used<br>
> before lnr<br>
<br>
Do we keep the lnr filename? Change to ln-python and add -r and -f?<br>
<br>
The above question wasn't answered. Should we just always force it and<br>
emit a WARNING if it's being replaced?</blockquote><div dir="auto"><br></div><div dir="auto">It’s should force replace it yes a note about replacing an existing file if any is fine </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
-M<br>
</blockquote></div></div>