On Mon, Feb 29, 2016 at 7:00 PM, Michael Orlitzky wrote:
> On 02/29/2016 06:24 PM, Andrew Udvare wrote:
> > On 29/02/16 03:23, Geaaru wrote:
> >>
> >> In conclusion, it seems that is not accepted use of nodejs modules
> >> ebuild inside portage. It is right?
> >>
> >>
> > There
On 02/29/2016 06:24 PM, Andrew Udvare wrote:
> On 29/02/16 03:23, Geaaru wrote:
>>
>> In conclusion, it seems that is not accepted use of nodejs modules
>> ebuild inside portage. It is right?
>>
>>
> There used to be a CoffeeScript ebuild if you search back. I do not
> remember how it worked but
On 29/02/16 03:23, Geaaru wrote:
>
> In conclusion, it seems that is not accepted use of nodejs modules
> ebuild inside portage. It is right?
>
>
There used to be a CoffeeScript ebuild if you search back. I do not
remember how it worked but IIRC I think it was basically just creating a
fake
Hi Andrew,
thanks for reply. My comment hereinafter.
On Mon, 2016-02-29 at 02:12 -0800, Andrew Udvare wrote:
> > On 2016-02-29, at 01:38, Geaaru wrote:
> >
> > Hi guys,
> >
> > I create an eclass that permit to create ebuild for nodejs modules
> > without define every times
> On 2016-02-29, at 01:38, Geaaru wrote:
>
> Hi guys,
>
> I create an eclass that permit to create ebuild for nodejs modules
> without define every times ebuild phases and avoid install of
> dependencies already present on system.
> My mission is create a module like