andreaferretti

Hi, author of the post here. I did in fact, update the post, mentioning your PR in the first paragraph.

I cannot really change the rest of the content: I am reporting the mail I sent, and that was it. Changing it after the fact would only add more confusion

Ok, thank you for the information. I will try to work from here :-)

I am having a similar problem (password sometimes required to shutdown or mount disks) with my latest Ubuntu, so I would appreciate a little more detail.

Do you happen to have a link to the arch wiki entry you are mentioning? What was exactly your problem?

Although I must add that probably the monolithic approach that is being used right now has helped a lot to avoid fragmentation

I admit I have not read into detail the above specification, but I think that an approach in the style of Metacello (from the SmallTalk community) would be simple to develop and fit Factor nicely.

There need not be changes to the way vocabularies are loaded: instead one can make some words that change the vocab roots according to some configuration files. One could have a FACTOR-ROOT/cache directory in addition to work, core, and extras, where packages are arranged by version. Then some machinery could set the right vocab-roots based on a specification.

One would need

- some words to create structure that describe packages (Maven-like). This would allow to declaratively say that my project, at version x, consists of this and that vocabulary, and relies on project foo at version y and project bar at version z

- some words to automate fetching the dependencies of my project recursively from common repositories (one could start with github)

- a word to set the vocab roots according to my dependencies

Ideally, I would like to write a configuration file that lists my dependencies and then do something like

    USE: my project.config
    myconfig set-deps

On top of this, one could develop GUI tools to automate writing specification files, or even suggesting officially endorsed packages. See for instance the GUI tools in Pharo for a great example of this.

The advantage would be that we would not have any changes to the way vocabularies are loaded, and the change would be much more incremental