Code Monkey home page Code Monkey logo

bonsai's People

Contributors

mitchweaver avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

bonsai's Issues

Remove `file` as core build dependency

currently we are using file to determine the compression type and whether is a tar archive, of downloads

This shouldn't be necessary as its given to us via the URL

add a `strip` function

the CFLAGS=-s and LDFLAGS=-s only work for stripping C-based executables as pointed out by people from the KISS project

To get around this, implement a function to use strip from bin/elf utils

------ also, find out how to get strip, as its not included by default in the toolchains gotten from http://musl.cc

port folders

currently ports are just in one big folder, this is already messy at ~60 ports -- can't imagine how cluttered it would be at 1000+

Some distros don't seem to think this is a problem, but I think it is.

Folder support such as core, opt, contrib as the likes of CRUX Linux or a similar style would be nice. Not sure how I want this implemented, just wanted to make this issue to note that is on the radar.

Redundant use of GNU

Under Core Philosophy, you state in point 3 about a better c library, "GNU GLibc" which is redundant. glibc is already GNU libc. It's like saying PIN number. You're basically saying "GNU GNU lib c.

get() does not support git

This is low priority due to any use of git requiring git as a dependency which is unideal. You should always try to use tarballs instead.

... With that said, I know some people will still want git for "bleeding edge", so it would be nice to add.

Add checksum to pkgfiles

I think it would be appropriate to add checksum (probably sha256) as a mandatory variable in pkgfiles. It should be checked against the downloaded file.
Currently, if package's server is hacked, the source file can be modified to be malicious. With checksum, this file is downloaded and then rejected.

github organization

should we create a bonsai github organization to store bonsai and bonsai-website? possibly others?

I see that bonsai by itself is taken but bonsai-linux is available, I think that we should use bonsai-linux regardless cause that's what the website is.

bug: some bz2 tarballs seem to not to be recognized as ustar

example: dropbear

sbase's tar complains that the format is not ustar and errors without extraction

  1. Is this fixable? Can we convert to ustar?
  2. Is this really the problem at all? Or is it a problem with bunzip2?
  3. Is it a bug upstream in sbase?
  4. Can we just find a different mirror? Perhaps with working bz2 or gz/xz?

-- I've tried #4, but every mirror is just a literal mirror of the same tarballs with the same problem

Ports: Wishlist

Use this issue to discuss ports that you wish to be added.


  • ghc
  • go
  • python3
  • python2
  • openvpn
  • dropbear
  • neovim
  • netcat
  • socat
  • nfs-utils
  • fff <-- (once we get the libedit patch upstream)
  • ranger (needs mouse support patched out for netbsd-curses)
  • plan9port
  • gnupg
  • offlineimap
  • neomutt
  • htop

Suggest your CFLAGS / LDFLAGS / etc

Always looking for good suggestions for more global flags to add to our .rc

Keep in mind these will be GLOBAL. So they must be sane, (ie not cause breakage).

Post them here for discussion / review.

(future): recursive dep handling for delpkg()

dependency handling works for adding packages, recursively gathering and adding the needed packages

it would be nice if this were the same for the delpkg() function

Note:

  1. only remove packages if they are orphans ie they have NO other packages depending on them
  2. Do not remove packages if they are part of a meta package such as core-system, (we dont want to remove our shell, coreutils, etc...)

We need a name.

distro is a placeholder.

Names are hard.

Give me your suggestions

allow to be run under `#!/bin/sh -e`

lots of things gracefully fail (on purpose) in the script, however this breaks -e
it would be nice/more secure if this were a possibility.

How to fix:

  • wrap statements in if / case
  • pipe the 1 exit code to a nop such as:

rmdir _non_existant_ 2> /dev/null ||:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.