ArchLinux package

[AeroNotix]

Hi,

https://aur.archlinux.org/packages/relx/
https://github.com/AeroNotix/relx-pkgbuild

Hope that helps,
Aaron

[ericbmerritt]

@AeroNotix Thats really cool. Is there something here I need to do though?

[AeroNotix]

Not really. My intention was to give 'ownership' to you guys, though.

[ericbmerritt]

The only problem with that is that we only infrequently use arch linux. That makes it a bit hard for us to maintain it.

[AeroNotix]

I'll maintain it, the code will be yours. The maintainership is in my name
on the AUR package site.

On Mon, Aug 5, 2013 at 9:55 PM, Eric Merritt notifications@github.comwrote:

The only problem with that is that we only infrequently use arch linux.
That makes it a bit hard for us to maintain it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-22136397
.

[jwilberding]

Cool, so you want us to clone that repo into erlware then and take pull requests from you?

[AeroNotix]

Yupp, sounds cool to me.

On Tue, Aug 6, 2013 at 3:12 PM, Jordan Wilberding
notifications@github.comwrote:

Cool, so you want us to clone that repo into erlware then and take pull
requests from you?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-22181281
.

[jwilberding]

@ericbmerritt Would you rather keep the whole repo or just incorporate the PKGBUILD file?

[ericbmerritt]

I am tempted to just incorporate the pkgbuild file, but I am wondering if that means we have to do the same for every other package management system out there. Lets keep it separate for now I think.

[jwilberding]

How about maybe a separate branch instead of separate repo?

On Tue, Aug 6, 2013 at 5:28 PM, Eric Merritt notifications@github.comwrote:

I am tempted to just incorporate the pkgbuild file, but I am wondering if
that means we have to do the same for every other package management system
out there. Lets keep it separate for now I think.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-22212953
.

[ericbmerritt]

I am not a big fan of separate branches for something thats going to be long lived. In my mind branches are just temporary variations of a mainline. So I think we can merge it in or keep it in a seperate repo. I am not super set against merging it in.

[jwilberding]

Until otherwise needed, I am just going to merge it in.

On Wed, Aug 7, 2013 at 9:28 AM, Eric Merritt notifications@github.comwrote:

I am not a big fan of separate branches for something thats going to be
long lived. In my mind branches are just temporary variations of a
mainline. So I think we can merge it in or keep it in a seperate repo. I am
not super set against merging it in.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-22250785
.

[jwilberding]

@ericbmerritt Please review/merge the 2nd one, ignore the 1st.

[AeroNotix]

Glad this got all sorted out, thanks guys. Hope it helps strengthen relx.

[tsloughter]

@ericbmerritt @jwilberding should we close this then?

[jwilberding]

Yep.

[AeroNotix]

Cool.