🐧 add a gentoo installation for mommy~

[Chery-cake]

I created a simple ebuild for gentoo, that installs the main branch of mommy.

The steps to install mommy are:
First you add the repository:
eselect repository add Sapphire git https://github.com/Chery-cake/Sapphire.git

Second you enable the repository:
eselect repository enable Sapphire

Third you need to unmask the package, just add the following to which ever place you prefer, inside /etc/portage/package.accept_keywords:
sys-apps/mommy ~amd64

Or you can add --autounmask-write to the install command and use dispatch-conf to unmask the package

And finally you can install mommy:
emerge sys-apps/mommy

[fwdekker]

that's super cool! thank you!

when i have a bit more time, i'll take a deeper look at this and will give a longer response :)

[fwdekker]

alrighty, i've read up a bit on gentoo, and tried it out in a vm. it works nicely! i'd love to make mommy available for all users on gentoo as well :)

that said, i don't want to tell users to trust an external repository that i have no control over. therefore, i want to suggest we move the ebuild into some place else. we have two options:

1. a separate fwdekker/ebuild-mommy repository, similar to apt-mommy, or
2. adding mommy to the guru repository~
   i think the second option would be really cool! now, i don't have a lot of experience with gentoo whatsoever. is adding the package there and maintaining the ebuild files something you would be interested in?

having said that, i do have a few minor comments about the current ebuild file:

1. your installation instructions weren't quite complete. for future reference, i used the following commands in a fresh, minimal(-ish) gentoo installation:

   sudo emerge app-eselect/eselect-repository
   # i used lowercase `sapphire` because you also used lowercase in your `profiles/repo_name` file,
   # and i got a warning otherwise
   sudo eselect repository add sapphire git https://github.com/Chery-cake/Sapphire.git
   sudo emaint sync -r sapphire
   echo "=sys-apps/mommy-9999 **" | sudo tee -a /etc/portage/package.accept_keywords/sapphire >/dev/null
   sudo emerge sys-apps/mommy

2. the license is listed as GPL-2, but mommy is licensed under the Unlicense, so you must list that correctly.
3. why does the ebuild have the keyword ~amd64? from what i gather, live builds typically do not have keywords at all (example: wine), and are therefore typically unmasked by accepting keywords ** for that package.

please do let me know what you think! if you're interested in maintaining the gentoo ebuild, then you should get in contact with the guru team to see what's what. if not, please also let me know, then i might do it myself~

[Chery-cake]

I'll answer in parts:

1 - I think it's a good idea to add mommy to guru, like you said it's a repository that is trusted by the community already.

2 - I'm new to creating ebuilds, so I could have made a few mistakes. I never noticed that live ebuilds weren't masked.

3 - I don't think I would be the best choice to maintain mommy on guru, I chose to make an live ebuild because I don't remember to check if my ebuilds are up to date on a reasonable time.

I would love to help you in creating the necessary ebuilds and installation guides

[fwdekker]

alright, fair enough. in that case, i'll see how far i can get myself with getting mommy onto guru, but if i have any questions or need your help, i'll let you know!