An OpenEmbedded recipe for salt is much more like salt-bootstrap than a
salt-formula in that it is a way to get salt installed on your system.
In the case of OpenEmbedded, it's actually baking salt into the initial
bootable OS image. This is welcome as salt is an efficient way to
manage embedded hardware, especially when unusual steps must be taken to
enable embedded peripherals like UARTs, SPI, and I2C. Having salt on
your first boot saves the step of bootstrapping.
Would it make sense to maintain the salt-openembedded repo as a part of
openembedded instead of as a product of saltstack? That way the
saltstack folks aren't evaluating pull requests for a technology that
isn't their area of expertise.
-Joel
On 2015-04-06 11:36, Joseph Hall wrote:
> Alejandro,
>
> I don't have an answer on that, but I will say that there are a
> couple of repos in that org that are reactors, not states. So maybe a
> salt-openembedded repo?
>
> Community: any thoughts?
>
> On Mon, Apr 6, 2015 at 9:38 AM, Alejandro del Castillo
> <
alejandro....@ni.com> wrote:
>
>> Hi Joseph,
>>
>> The thing is that the Salt recipe for OpenEmbedded is not a Salt
>> state (my
>> understanding is that Formulas are states). It is a file that
>> defines the
>> way to create ipk,deb and rpm's out of Salt source. Specifically, I
>> wanted
>> to submit my Salt recipe (
salt_2014.7.1.bb [1]) on the
>> [2]
>> .
>>
>> If it's ok for me to submit
salt_2014.7.1.bb [1] on
>>
https://github.com/saltstack-formulas [3] to review the bb file, I