-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loggers #117
Comments
Agreed, would clear up any possible future confusion. |
I don't remember if @RecursiveForest intends to keep developing morituri-whatlogger but being it only compatible with whipper it can be easily renamed without too much thought. |
Well if @RecursiveForest is OK with that, I can fix whipper-eaclogger-git when required. |
@JoeLametta Before long morituri won’t even be possible to install on any distro, so… Not sure whether it’s worth keeping the old loggers targeting only it. |
Right now it isn't so hard to keep them compatible: what you're saying is right but morituri is still available on Debian Jessie (which will be supported until 2020) and it can probably be installed / compiled on other distros too (CentOS?)... I think the right time to end morituri support will be as soon as we've got whipper natively packaged by the main distributions. |
FWIW, any "morituri" loggers will need to be updated since #109 as whipper will no longer pick up loggers installed for morituri. |
@RecursiveForest Is morituri-whatlogger still maintained / useful? |
All maintained loggers have been updated and moved to the whipper-team organization: I'll update whipper's README with the updated reference. P.S.: I think morituri-whatlogger won't be developed anymore. |
morituri starting to be dropped from distributions (because of gstreamer0.10), I think that the loggers should start being named
whipper-<loggername>
instead ofmorituri-
. This would be more explicit and understandable for new comers.I’m posting this here since this is a whipper related issue, but I’m especially targeting @RecursiveForest and @JoeLametta who happen to maintain most (if not all) of the external loggers.
The text was updated successfully, but these errors were encountered: