Refresh CoreCDP repository from OpenEmbedded?
Home › Forums › MultiConnect OCG › Refresh CoreCDP repository from OpenEmbedded?
- This topic has 6 replies, 3 voices, and was last updated 13 years, 2 months ago by Ken Bannister.
-
AuthorPosts
-
September 7, 2011 at 8:59 pm #2626Ken BannisterParticipant
Do you have any plans to refresh the MultiTech CoreCDP git repository from the OpenEmbedded repository?
I found several issues when building from the git instructions on the CDP 1.1.1 release page [1]:
1. binutils v2.18 fails due to an MD5 checksum failure. Apparently the source repository recently repackaged this old version.
2. Unable to fetch update-rc.d from the handhelds.org CVS repository. OpenEmbedded trunk now provides that file itself rather than retrieving from handhelds.org.
For now I will build from CDP 1.1.1 download.
I understand that link rot is to be expected from the fork from OE in January 2010. It seems that it may be about time to refresh from their repository.
Thanks,
Ken
September 8, 2011 at 9:49 pm #3358Jesse GillesBlockedKen,
Yes, there are plans and work is currently in progress to release a new CoreCDP version based off a new OE snapshot (currently will be based off the 2011.03 branch).
Also, source code is mirrored on multitech.net:
http://www.multitech.net/corecdp/sources/
The build process is supposed to fall back on this as a source when other locations fail, but if you get a new file with a different MD5 sum, it obviously doesn’t help.
Jesse
September 9, 2011 at 6:24 pm #3359Ken BannisterParticipantThanks for the update. I do not recall seeing the fallback to multitech.net, and plan to investigate.
For the next release, as a community member I would appreciate seeing as much of the development as possible in the open — in the public repository. I don’t see much happening at present on git.multitech.net.
September 10, 2011 at 10:46 am #3360Ken BannisterParticipantTo follow-up on the update-rcd package, the MultiTech http mirror does not include this package. The package is retrieved by cvs protocol.
Outdated sources are a real pain. :-/
September 16, 2011 at 1:16 am #3361Brandon PedersenParticipantFor the next release, as a community member I would appreciate seeing as much of the development as possible in the open — in the public repository. I don’t see much happening at present on git.multitech.net.
I agree, that would be nice…I was weary of development on this platform going stale. Good to hear it is still being worked on.
September 16, 2011 at 6:33 pm #3362Jesse GillesBlockedMessage received. I am reorganizing the new release into a bitbake layer rather than a custom branch, so it will be in a new repository completely. I am planning to move the current internal git repo onto git.multitech.net soon. We are still doing testing internally so it’s not release ready quite yet.
You can be assured the development platform is definitely not going stale 🙂
Jesse
September 19, 2011 at 8:19 pm #3363Ken BannisterParticipantJesse, I appreciate MultiTech’s responsiveness to user requests. Use of an OE machine layer sounds like the appropriate way to leverage the platform to stay current with upstream. Thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.