Original date:2015-09-14 17:30:36 Edited by: xecronix Subject: EuAnyRepo vs EuDrop... what's the difference?

Forked from Complete Guide to Using DLLs in OpenEuphoria

ghaberek said...

Speaking of package mangers for Euphoria. I have like the name euget better. Maybe we should have a vote or a naming contest.

I like the name EuDrop Project but I'm not married to it. I think getting the community involved and excited about the project via a naming contest is a great idea. Do we have any volunteers to set up a "Survey Monkey" or something to vote on the name?

ghaberek said...

I also think this package manager should include all of the functionality described by EuAnyRepo. Why would these be two separate projects?

Who is your customer?


Honestly EuAnyRepo is meant to solve Linux only problem. The "problem" software developers have when developing software for the Linux problem is whether or not certain 3rd party software (or library) is actually installed on the target system. If it isn't, how do you get it installed for the end user? Is it a yum command, dnf, apt-get, or something else that's required to get some third party software installed for my user?

Unfortunately, currently I'm unaware of a software repository for Windows users. Sadly, the closest thing to a software repository my Windows brethren have is Google. They are forced to scour the net looking for tools and apps that are installed via installers and zip files that may or may not be smart enough to recognize a dependency. Or perhaps they are monolithic in nature? Even if my brethren actually purchase the software they require, there is no reasonable expectation that the software will automatically install 3rd party requirements.

In short, EuAnyRepo is intended to be for package managers (Apt, Yum, Dnf, ???) what jquery is for javascript. A nice abstraction sitting on top of the different package manager implementations. It's a cool tool but honestly it doesn't solve any Euphoria specific problem. Especially across multiple non-similar platforms.


If you buy into the EuDrop Project solution you're probably a Euphoria application developer. You want something like CPAN or Ruby Gems. You want/need tools and libraries that are easy to find, install and use. In fact, if the install and use process can be automated, even better. You realize that you may or may not even have access to install libraries in a global location (like /usr/local/share for example). When you're done writing your software, you don't want to go through some sort of complicated sleuthing exercise to package up your software for your customer.

If you're a Euphoria Library developer (or a C lib wrapper), you would buy into the EuDrop Project because you don't have time to answer support questions like, "How do I install this coollib thing?", "I included coollib.e but open_dll failed? Where is the dll?", "Thanks for the coollib but it just suddenly stopped working. Can you help?" Additionally, you want to help the community but you don't want to be troubled with infrastructure concerns like hosting, version control, update announcements, etc. You just want to code.


I haven't written anything about this yet but basically, it's like bundler for Ruby. If you buy into this solution, you're an application developer that doesn't see the need for packaging your app at all (except for the code you wrote yourself, of course). You want to provide a list of dependencies and you expect some tool to go get 'em. This might be a pipe dream, but that would be the goal if EuDrop gets stable. In short, this tool would essentially become a EuDrop aggregation tool.


Another tool that's in my head but not written down yet. It is like rvm. But it's too far away for me to think about yet.

Not Categorized, Please Help


Quick Links

User menu

Not signed in.

Misc Menu