Re: EuAnyRepo vs EuDrop... what's the difference?

new topic     » goto parent     » topic index » view thread      » older message » newer message
ghaberek said...

This sounds like a library and not an application. In fact, it sounds like a really good idea for a library to me. And on supported systems, that library can be used to manage system-wide dependencies as necessary. In fact, I'm not even aware of any library that aims to satisfy this requirement and it doesn't sound terribly difficult to me.

Thanks, the idea from this thread The basics are working at this point on Fedora. Maybe a couple more hours of coding and testing this thing should reach beta. And it is a library, not an app.

ghaberek said...

The solution for this is already established: we manage everything ourselves. ...

There are, of course, some licensing restrictions with that method, so the other option is that we look for the dependencies and then tell the user to go hunt that down and come back later.

You are right, but what we're talking about here is a game changer. And a Super Awesome reason to choose OpenEuphoria over another tool. If we can learn from the several projects that have tried this so far, (Ruby, Python, Perl, PHP) and learn as much as we can from Apt and Yum we could be discussing the killer app for Euphoria right now.

ghaberek said...
xecronix said...

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 installer and dependency management tool.

I see where you're going with this but again, this sounds like a function of the package manager. It's really just a matter of having an extra export function to create deb, rpm, or exe installers.

This is the point where I realized where our points of views are in contrast. You are thinking about building a tool that can generate a package like an rpm, deb or exe installer. Right? Im thinking a EuDrop is the Euphoria equivalent of an rpm or deb package.

In debian terms: EuDrop Project about building a package, metadata, and some kick butt tools to make building these things as simple as possible. In other words, this project is about building the Euphoria equivalent of a .deb file.

EuBundleIt If this project gets wings one day, this is about building the apt-get equivalent for EuDrop files.

The end user, developer or otherwise, would most likely interface with the system using something patterned off of synaptic. And like synaptic sits on to of apt-get, Our GUI would sit on top of EuBundleIt.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu