Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors in README #116

Open
riban-bw opened this issue Dec 2, 2020 · 6 comments
Open

Errors in README #116

riban-bw opened this issue Dec 2, 2020 · 6 comments

Comments

@riban-bw
Copy link
Contributor

riban-bw commented Dec 2, 2020

The git repro README says a dependency to build under Bodhi is libpng12-dev but this package does not exist in the current or next version of Bodhi. I guess this should be libpng-dev. Also, could you make the list of dependencies a single line rather than three to allow simple copy and paste?

@riban-bw
Copy link
Contributor Author

riban-bw commented Dec 2, 2020

Further: There is a "Must:" section which does not make sense to me. It isn't clear what a user must do with this list. Then the instruction to install just says to use ./configure but this is not part of the git repo. What further instructions are required to build and install Moksha from source.

@riban-bw
Copy link
Contributor Author

riban-bw commented Aug 13, 2021

I believe these are the steps to build from git:

sudo apt install doxygen pkg-config libglib2.0-dev libssl-dev libpng-dev libharfbuzz-dev libfribidi-dev libfontconfig1-dev libluajit-5.1-dev libsndfile1-dev libpulse-dev libbullet-dev libxcb1-dev libxcb-shape0-dev libxcb-keysyms1-dev automake libx11-xcb-dev libefl-dev libedbus-dev libtool libasound2-dev
git clone https://github.com/JeffHoogland/moksha.git
cd moksha
./autogen.sh
make

@mckaygerhard
Copy link

hi, umm older issue .. i foun several missing here also..

seems this git is not enought to get full moksha desktop

@rbtylee
Copy link
Collaborator

rbtylee commented Jan 14, 2025

For Ubuntu or Debian you can find the needed info in the control file we use for moksha in BL7. Note libefl-dev is Bodhis EFL package so if you want to use Ubuntu or Debians version of EFL you have to install (or compile) the needed EFL libraries. I suggest if compiling just compile it all.

Also note moksha-menu and bodhi-theme-moksha-green are found elsewhere and need to be installed at least if you want our theme and menu.

Bodhi-bins-default is not really needed but you can see what it installs here.

elaptopcheck is certainly not needed mostly used when installing Bodhi using our ISO. Gtk-recent is also not needed but it does add some support for that functionality. But Bodhi-quick-start is needed as it is used by our help entry in the menu.

@rbtylee
Copy link
Collaborator

rbtylee commented Jan 14, 2025

Ideally, most of this should be added to repo so it is more self-contained. And in a perfect world someone would take the time to update the readme as well as move this whole repo to BodhiDev. Jeff would have to move the repo as no one else can. And considering we have only 2 devs that work on Moksha this issue (updating the readme) is of low priority. This may seem harsh but we really lack the time to do all the stuff we HAVE to do in order to keep our distro alive.

@mckaygerhard
Copy link

ok basically the repository has lack of information . so in conclusion (It's actually worse...) as an independent project it doesn't have absolutely all the information necessary to get where it should... libefl-dev on most linux is not packaged and there is not references from README..

me or anybody (I can) help with that of course, but waiting for a pull request to be able to move forward should be a little faster..

umm ok so there are the questions for the organization:

  1. the missing parts can be forked too? i mean: project itselft does not have the information nor the references necessary to have all the power of the desktop in all its splendor
  2. otherwise, is the project a fork for new desktop or just a part of another project.. i noted you mentioned references to Bodhi linux.. as i noted due the missing information it looks like part of another more bigger project

of course based on those two questions we or you (as you like of course, if dont like my proposals) should organize all artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants