search

vectrixdevelops / mpg123-mirror

A mirror of the original mpg123 found on svn. DO NOT PUSH TO THIS REPOSITORY.
Other
1 stars 1 forks source link

Transfer to audiojs and mb add some scripts for autoupdate? #2

Open dy opened 6 years ago

dy commented 6 years ago

Hi @connorhartley!

It feels like @audiojs needs resolving the issues with abandoned components, like audio-speaker. Since audio-speaker@2.0 heavily depends on mpg123, how about keeping this svn mirror in @audiojs and organizing some scripts like npm run sync to fetch the latest svn? Can you show how do you sync with mpg123 svn?

Also - is that necessary to keep the fork, maybe if that is possible to just have direct mpg123 dependency? Otherwise we may need to marge fork with this mirror every sync.

Appreciate your help!

vectrixdevelops commented 6 years ago

I will transfer this and write an issue on how to update it, but the issue with the fork is that the mirror here must be the same as the upstream and I had to make some quick fixes to fix Windows compatibility IIRC. Although I should have still emailed the mpg123 team to see if they could add the changes themselves, so I will see what I can do there.

vectrixdevelops commented 6 years ago

It seems the compatibility changes I made, they've already added. So I don't think we need the fork anymore. I will remove that and transfer this, soon.

dy commented 6 years ago

Hey @connorhartley! Is there anything I can assist with moving on with this? I think we need that in https://github.com/audiojs/audio-mpg123/pull/10 for progress. Btw have you received the email? I used your email address from your github. Cheers!

bvarba commented 6 years ago

Hey @connorhartley, great work! I'd be happy to jump in on this. Would this be enough to have sync script: https://stackoverflow.com/questions/7861160/how-to-mirror-trunk-of-svn-repo-into-github

vectrixdevelops commented 6 years ago

Sorry I've been quite busy this week and will get to this on the weekend.

@dfcreative @bvarba I did receive your email and will be happy to create instructions on migration as an issue on this repository when I transfer it this weekend to @audiojs. We cannot make changes to the mirror unfortunately as that will conflict with migration (hence the previous need for a fork), but I think we can manage just the mirror as the people at mpg123 have already made the changes we had made on our fork to fix Windows compatibility and various other issues themselves and would be active enough to fix things if we notify them by email pretty quickly from what I've seen.

I'll add to this more on the weekend, thanks for your patience. 😄