Axoloti TEST release 1.0.10

#62

4 posts were merged into an existing topic: Improvements/Wishes for the patcher

#66

Ooops, yes, sorry. Not so much a bug, more of a feature-request, I suppose.
Could you possibly move my posts to there? If not, I will do it myself by copy-paste.

a|x

#67

Scrub that, what you wrote in that thread pretty-much covers it, I think.

having said that, I do consider the hidden folders showing at / a bug.

a|x

#68

No problem.
Ive already added a post which i think mind of covers it, also with a user link to apples recommendations.

in a similar vain, I think we need to be careful with bugs, that are not specific to 1.0.10.
(my intention for this thread was mainly for issues we have introduced in 1.010, by new features etc)

my concern, is no one has the time to trawl various threads, in particular long ones like this, and once this is closed it will likely be forgotten.

for existing bugs, they probable should dedicated helpdesk threads ... and we probably need to get these bugs into github issues.... its not practical to track bugs here.

basically, if its unclear if its a bug, vs user error, or feature request, raise it here to be discussed...
if not then i think it needs to go directly in github issues so it can be tracked.

#69

Sorry...... :wink: ..............

#70

It's hard to know if a bug was introduced in a new software version, though. It could easily be that it was there before, but you never stumbled across it because you'd never gone through that exact sequence of actions previously.

a|x

#71

yeah, I know , usually its about... has this area of functionality changed? (which we do try to list)

with 1.0.10 you are able to keep multiple copies of axoloti on your computer, so you can actually run 1.0.6 and 1.0.10 and see if its existing in 1.0.6. of course this assumes you can reproduce reliably and easily, but going thru that step is useful for devs anyway, as they need to be able to reproduce.

honestly, though with 1.0.10 its not a big deal, as I think most 'heavy' users are now on 1.0.10, so its almost 'defacto' released. its not ideal from a software engineering viewpoint, but its proven pretty tricky to get out the release, the longer the test has gone on, the more features were 'added' whilst we fixed 'critical bugs' and this formed a vicious circle, which unfortunately we have not quite broken free of yet.
which is why I'm kind of trying to separate stuff out into this release, and after.

unfortunately, Ive seen this on many open source projects, you get into a cycle, when there a perpetual unstable/beta/alpha release that everyone uses, since the last official release is years old. Its not healthy, as it kind of then mean half finished features and bugs are 'tolerated', since its an 'unstable/dev release' - and eventually, there are so many unfinished things, it actually becomes impossible to ever put out a proper release again :frowning:
hence why I'm keen to break the cycle

#72

This is most likely caused by an incomplete download/extract. The installer downloads a few zips/tgz's, and if the file already exists, it skips the download, when it is incomplete, extraction will fail. Likewise, when the extracted folder corresponding to the download already exists, it skips extracting all files again.
Compiling as root is not needed, and could cause permission issues if you try compiling without root permissions again.

#73

Yes, that looks correct, I have pushed this to axoloti-factory, sync libraries and the fix will be fetched.

#74

Thanks, for the followup. However in opensuse, I have never been able to compile as a user. I have to modify the build file (as I posted some time ago), and there is something else (is it the UPD rules?) that fails as well.
You are right that some files ownership needs to be changed so it can be run by the user.

#75