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 » U++ TheIDE » U++ TheIDE: Other Features Wishlist and/or Bugs » TheIDE remote package dependencies proposal - dealing with baazar
Re: TheIDE remote package dependencies proposal - dealing with baazar [message #49911 is a reply to message #49906] Mon, 04 June 2018 09:59 Go to previous messageGo to previous message
mr_ped is currently offline  mr_ped
Messages: 826
Registered: November 2005
Location: Czech Republic - Praha
Experienced Contributor
The proposed "remote" looks to resemble some things like artifactory/etc, where the "remote" packages are locally residing in some hidden directory in some cache.

I prefer to build from sources everything, and if I already have source somewhere, I prefer ordinary common location, like "bazaar", not some temporary cache. Also for important projects I keep all required sources (including framework libraries) in the project git, so I can be sure, that I have everything available even 15 years later, if for whatever reason I will need to rebuild the project (and I will have to fight hard only with the obsolete build tools, not also hunting down some old variants of libraries).

This policy is result of my personal experience, how I got burnt over years with my old work, which is now impossible to restore/update.

I guess the "cache" thingy with remote updates makes sense for binary distribution (like jar/aar/war archives in Java and Android world), but even there we often download the packages separately, and put them into project locally (and into git), so again the project git is self-contained, and doesn't need any remote server to be built. It makes the situation somewhat messy when you need to update the third party libraries often (like they are in development), but for most of the time it works reasonably well.

So I believe your proposal goes exactly in opposite direction ("without manually copy it to my project"), and I'm not interested.

But BTW, if you have the packages like in "bazaar" nest, and you have your apps nest configured to use that for build, you don't need to copy the bazaar package to your project nest, it will build from original bazaar location, so the UPP looks to solve this aspect (no need to copy manually) well.

[Updated on: Mon, 04 June 2018 10:00]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Include full year in build_info.h instead of two last digits
Next Topic: [PROPOSAL] Redesigned Assembly Setup Dialog
Goto Forum:
  


Current Time: Sun Jul 06 19:47:58 CEST 2025

Total time taken to generate the page: 0.04327 seconds