| Summary: | Update DirectFB to git? | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | graphics | Assignee: | Maxin B. John <maxin.john> |
| Status: | RESOLVED FIXED | QA Contact: | Libertad <libertad.gonzalez.de.la.cruz> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | alex.kanavin, alexandru.c.georgescu, bluelightning, jose.perez.carranza, liezhi.yang, meta.mr.watcher, meta.watcher |
| Version: | 2.0 | ||
| Target Milestone: | 2.2 M2 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Ross Burton
2015-10-12 16:13:10 UTC
Looks like it re-appeared at Github: https://github.com/deniskropp/DirectFB Fine, re-titling this to remind us to fix the recipes to use the new git upstream repos if directfb.org doesn't come back. Reassigning to Content. Whilst it looks like directfb has moved to some random github clone that claims to be official, it's *not* the directfb project on github. Probably worth bringing this up on oe-core/oe-devel and considering the lack of activity on the recipe in oe-core if there's any interest in keeping it in meta-oe or if we should just ditch it. *** Bug 8751 has been marked as a duplicate of this bug. *** I asked them what happened to the website: https://github.com/deniskropp/DirectFB/issues/3 I might just be paranoid but let's be careful about the github account and repo: there does not seem to be a single verifiable connection (like email address or other account) that would connect these to the old directfb.org project. Moving to M3: I'm still not sure what to do though... * The new github repo does not even include the latest release tags and developer seems unresponsive so (in combination with the doubts in previous comment) using that repo seems unwise for now * on the other hand some people really want directfb So nuke directfb or keep it? My proposal (on the mailing list http://lists.openembedded.org/pipermail/openembedded-core/2016-January/116077.html ) was to remove it at the beginning of next development cycle if nothing changes. Even though I'm certain it's truly dead, we need a grace period so that people stop pointing to the new repo as counter-evidence. So you can set the TM to 2.2. Agreed, there's still users out there so lets give them the 2.1 cycle to actually have a git repo that contains the latest releases and so on. If in 2.2 then there's been no change then there's a stronger argument for removal. Thanks for the link: I somehow managed to miss most of the discussion when it happened. 2.2 it is then. Hi Jussi, I'm sorry, I did a wrong action just now, I set the target milestone to M2, but I shouldn't, you can feel free to change it as you like. I updated it by a mistake. As of now, no change in upstream situation whatsoever. Right, I propose we rip directfb out of oe-core and submit the recipes to meta-oe. This was the opportunity for people to fork and restore DirectFB, and it didn't happen. A couple of random github clones has 1.7.7 release tag: https://github.com/deniskropp/DirectFB/issues/2#issuecomment-226316231 Also, Andre McCurdy's recent patch shows that there are still some users for DirectFB. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2a85038dd03463774fb787b655887297ec4f0a04 So, I would support moving directfb recipe from oe-core to meta-oe. sent directfb removal from oe-core RFC and patches: http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123401.html |