Kristian Fiskerstrand writes:
> inherited eclasses. having a whitelist in place and die if eclass is not
> updated to handle it solves it.
>
> Thoughts? comments? cookies? threats?
Wouldn't a blacklist be more practical than a whitelist?
root# cat /usr/portage/profiles/eclass.eapi.mask
foou
At Sun, 10 Mar 2013 16:57:07 -0500,
Matthew Thode wrote:
>
> Starting up a new project (gentoo-openstack). It is currently a
> subproject of virtualization and our project page can be found here.
>
> http://www.gentoo.org/proj/en/virtualization/openstack/
>
> The current goals are to flesh out
I haven't used or updated this package for a long time. However
upstream is still active and there are some users.
I've removed myself as maintainer and changed bug ownership to
maintainer-nee...@gentoo.org
Thanks,
Erik
# Erik Mackdanz (6 Feb 2019)
# Dead upstream #677400
# Masked for removal in 30 days.
sys-fs/cloudfuse
l request.
Any Github presence of the tree will result in Github issues being
submitted and Github pull requests coming across. We'd have to be
prepared to chain that into our existing processes or have someone
dedicated to closing every issue/pull request with "Use bugzie".
--
Erik Mackdanz
e
activity since 1G is hard to achieve (no portage tree!) and m1.tiny's
aren't useful generally.
Thanks for considering these enhancements for future builds. I'd love
to hear feedback on any of these suggestions.
--
Erik Mackdanz
