Pramod V U <pramodvu1...@proton.me> writes:
Soon, I will be back with an ebuild.
Will also PR on github for inclusion into repo...
Great, thanks!
A few things to consider, if you're not already aware of them:
* All of 66's dependencies will need to be packaged as well, if
they're not already available.
* Are you willing to become a proxy maintainer for 66 and any
currently-unpackaged dependencies?
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
One reason a package might not get added to the main repo is not
that no-one has created an ebuild, but that no-one is willing to
commit to maintaining that ebuild, i.e. actively following
upstream updates and issues. An ebuild added to a repository
without anyone committing to maintaining it can create problems
for (a) Gentoo devs, who end up being forced to take on extra
volunteer work; and/or (b) users, who can't rely on that ebuild
getting security and bug fixes etc.
Depending on the situation, the package might more appropriately
be added to the GURU repository:
https://wiki.gentoo.org/wiki/Project:GURU
https://wiki.gentoo.org/wiki/Project:GURU/Information_for_Contributors
* At any rate, be sure to run pkgcheck on your ebuild:
https://wiki.gentoo.org/wiki/Pkgcheck
Alexis.
