Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » [Proposition] Simply source package manager for Upp
[Proposition] Simply source package manager for Upp [message #54236] Sat, 13 June 2020 22:18 Go to next message
Klugier is currently offline  Klugier
Messages: 660
Registered: September 2012
Location: Poland, Kraków
Contributor
Hello,

I would like to start the discussion about adding simply source package manager for Upp. The general idea behind it is to add easier way of consuming 3-rd party code. For example, I would like to use Oblivion's MessageCtrl or TerminalCtrl. Right now I need to copy that source code from GitHub to one of my assemblies and consumes it there. Of course such approach is problematic due to the need of manual work like coping file, also updating such package requires additional manipulations. My idea assumes that this work can be simplify by specifying the GitHub repo link with the version (latest by default). Here is my proposition to .upp file modification:
description "Rudimentary HelloWorld application with menu and status bar\377";

uses
    CtrlLib;
        
uses_remotes
    https://github.com/ismail-yilmaz/message-ctrl.git@master;
    https://github.com/ismail-yilmaz/terminal-ctrl.git@1.40.1;


file
    hello.cpp;

mainconfig
    "" = "GUI";


In the source code, all you need to do is to include this packages like the regular ones
#include <MessageCtrl/MessageCtrl.h>
#include <TerminalCtrl/TerminalCtrl.h>

// ...



It will require one repository per package. Repositories that will aggregate several packages will be prohibited.

The general idea is exactly the same as we can see in golang. It is source only package manager without binaries. Precompile binaries support can be added in the future, however it is not critical right now.

Adding simply package manager will encourage developers to create their own packages. In the long term it will mage Upp much stronger with bigger community engagement. Moreover, it will be huge opportunity to clean bazzar.

I would like to here what do you think about such improvement.

Sincerely,
Klugier


Ultimate++ - one framework to rule them all.
Re: [Proposition] Simply source package manager for Upp [message #54237 is a reply to message #54236] Sat, 13 June 2020 23:13 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3148
Registered: August 2008
Ultimate Member
I am not able to understand this obsession against Bazaar, as it gives consistency to U++ supporters effort, that if not, it could be dispersed in different external repositories. I would ask Mirek not to lose this cohesion.

However, if it is decided that GitHub is going to be the main repository for U++, Klugiers's proposition, or something similar, would have to be sooner or later implemented.

In fact, I have felt myself in this situation today. If you expect to deploy your project in GitHub, like BEMRosetta in my case, today it is a problem to deploy your sources with U++ in a coordinated manner so user can get and compile updated sources properly.


Best regards
Iñaki
Re: [Proposition] Simply source package manager for Upp [message #54241 is a reply to message #54237] Sun, 14 June 2020 00:35 Go to previous messageGo to next message
Klugier is currently offline  Klugier
Messages: 660
Registered: September 2012
Location: Poland, Kraków
Contributor
Hello Koldo,

Quote:
I am not able to understand this obsession against Bazaar, as it gives consistency to U++ supporters effort, that if not, it could be dispersed in different external repositories. I would ask Mirek not to lose this cohesion.

I would like to thank you for your feedback.I think there is no obsession against Bazaar. It is good project, however we can handle it better and in more decentralize manner. Moreover, all packages can be developed independently. Even if we remove Bazaar from upp distribution, it doesn't mean that we will stop promoting Bazzar packages. Their packages should be present on website and there should be the possibility to download Bazzar examples from TheIDE.

Quote:
However, if it is decided that GitHub is going to be the main repository for U++, Klugiers's proposition, or something similar, would have to be sooner or later implemented.

It is just a proposition, however as we want to grown. We should focus on making upp a platform that is easy to expand.

Quote:
In fact, I have felt myself in this situation today. If you expect to deploy your project in GitHub, like BEMRosetta in my case, today it is a problem to deploy your sources with U++ in a coordinated manner so user can get and compile updated sources properly.

Optimally with the package manager we should be able to overcome this issue. You should have single script/makefile/cmakelist that will download umk, package manager and target upp platform. So, .upp file should support remote assemblies. Here is some conceptual proposition:
description "Rudimentary HelloWorld application with menu and status bar\377";

uses
    CtrlLib from remote uppsrc; // <- Remote assemblies support...
    MessageCtrl from remote;
    TerminalCtrl from remote;
        
remotes
    https://github.com/ultimatepp/uppsrc.git@2020.1;
    https://github.com/ismail-yilmaz/message-ctrl.git; // <- If version not specified use latest master version
    https://ultimatepp.org/ismail-yilmaz/terminal-ctrl.git@1.40.1; // <- You should be able to use any git provider not only GitHub

file
    hello.cpp;

mainconfig
    "" = "GUI";


The version compatibility and dependencies should be designed with careful. Please notice that some other remote packages can have dependencies, too. So, we should be extremely careful. We do not want to create dependency hell Smile

Sincerely,
Klugier


Ultimate++ - one framework to rule them all.

[Updated on: Sun, 14 June 2020 00:38]

Report message to a moderator

Re: [Proposition] Simply source package manager for Upp [message #54248 is a reply to message #54241] Sun, 14 June 2020 19:46 Go to previous messageGo to next message
Oblivion is currently offline  Oblivion
Messages: 692
Registered: August 2007
Contributor
Hello,

As a long time U++ user, allow me to state my initial stance (before we delve into any discussion) Smile

1) I get the impression that the proposed approach has a potential to break things in TheIDE, umk, and/or makefiles.
Because it seems to require heavy patching and has a tendency to get overly complex. (I may be wrong, of course.)

2) Bazaar is a nice way to keep extras in one place. So I agree with Koldo here.

2) OTOH, I do think that at least TheIDE can do better. At least there should be an easy way to download, set up, update, check, remove GIT/SVN/etc. repos as assemblies, nests, or packages, in a guided manner ("next -> next -> ok", I mean.). This can be done in the main package selection screen of TheIDE and later via a file menu item. In short, IMHO the main package selection screen should allow users to manage their local/remote assemblies/packages/nests as transparently as possible.

I believe this general approach can provide a smoother way to achieve something similar to "remotes" integration. In this way, say a remote git repo, could be direcly cloned as an assembly/nest/package and can be worked on locally. But we'll get the chance to update the local copy periodically, push changes if we have a write access, etc. Since the latter already exists in TheIDe in some form, however rudimentary, all that has to be done is to polish the existing svn/git integration and then write a good repo setup dialog (next->next->ok) which will present the user with options to set up the repo as assembly, nest or package, and which can serve to both new and experienced U++ users.


P.s. I am not very happy about the overall file structure of upp-components. I am going to overhaul and polish it with -hopefully- Upp's 2020.2 release (and sync with it thereafter, using only a dev branch to add new stuff in the meanwhile), Still I think agregating packages in a repo is better for me than having a repo for each package (given that I am going to publish new packages and some other tools/apps in the near future)


Best regards.
Oblivion



[Updated on: Sun, 14 June 2020 20:49]

Report message to a moderator

Re: [Proposition] Simply source package manager for Upp [message #54249 is a reply to message #54248] Tue, 16 June 2020 17:27 Go to previous message
mirek is currently offline  mirek
Messages: 12581
Registered: November 2005
Ultimate Member
I agree with general concept, not so sure about details... Smile I think it should be a bit more like Oblivion's suggestion. That is, keep basic structure unchanged and add another level of metainformation to download dependencies.

Also, being there, it would be nice to have some sort of "distributed protocol" to have a list of downloadable "remotes" in theide.

Either way, I am adding this to a long list of things I am thinking about Smile

Mirek
Previous Topic: SSE2 and SVO optimization (Painter, memcpy....)
Next Topic: TheIDE crash after switching package
Goto Forum:
  


Current Time: Wed Jul 15 03:04:56 CEST 2020

Total time taken to generate the page: 0.01972 seconds