Git Product home page Git Product logo

ineluctable-overlay's Introduction

Ineluctable Overlay

Build Status

Ineluctable Overlay offers a repository of Gentoo ebuilds maintained by me for projects that are not yet available through the Portage tree.

Managing This Overlay

This section will show you how to install the Ineluctable Overlay into your Gentoo system, hence the following instructions assume a certain level of expertise using Portage.

Install

As per the current Portage specifications, ebuild repositories (a.k.a. overlays) can be managed via file collections under /etc/portage/repos.conf/.

To enable this overlay, you first need to have git installed:

emerge --ask --verbose dev-vcs/git

Then you need to add this overlay to the Portage sync system, by downloading the ineluctable-overlay.conf file:

wget https://raw.githubusercontent.com/Dr-Terrible/ineluctable-overlay/master/ineluctable-overlay.conf \
	-O /etc/portage/repos.conf/ineluctable-overlay.conf

Using Packages from ::ineluctable-overlay

To start using this overlay, you need to download the entire ebuild repository via:

emerge --sync ineluctable-overlay

Uninstall

To uninstall the overlay, simply run:

rm /etc/portage/repos.conf/ineluctable-overlay.conf
rm -r /var/db/repos/ineluctable-overlay

Disclaimer

Keep in mind that this overlay provides packages that differ from the ones in the Portage tree.

If you do have troubles with an ebuild provided by this overlay, please take it up with the ebuild provider (the owner of this GitHub account) and not with the official Gentoo's developers. In short, in case of issues, please DO NOT report bugs at bugs.gentoo.org for these ebuilds.

Supported Architectures

This repository offers packages that are known to work on the following architectures:

  1. x86 (32bit)
  2. amd64 (64bit)
  3. arm
  4. arm64

Contributing

I welcome issue reports, feedbacks, and ebuild requests; I encourage you to use the issues list on GitHub to provide them.

Code contributions and bug fixes are welcome too, and I encourage the use of pull requests to discuss and review your ebuild code changes. Before proposing a large change, please discuss it by raising an issue.

Before You Begin

This overlay assumes that you have read, and properly understood, the Gentoo Developer Manual.

Code of Conduct

Help me to keep this overlay open and inclusive for everyone. Please, read and follow the Code of Conduct.

Making and Submitting Changes

To make the process of pull requests submission as seamless as possible, I ask for the following:

  1. Go ahead and fork this project and make your changes.

  2. When your code changes are ready, make sure to run repoman fix -d, repoman full -d, and repoman -vx full in the root of the repository to ensure that all the Gentoo's QA tests pass. This is necessary to assure nothing was accidentally broken by your changes; for the purpose, this GitHub repository integrates Travis for Continuous Integration of repoman tests. I only take pull requests with passing repoman tests.

  3. If your commits are all related to the same ebuild, it's advisable to squash then into a single one with git rebase -i. It's okay to force update your pull request with git push -f, if necessary.

  4. Make sure your git commit messages are in the proper format to make reading history easier. Commit message should look like:

    [category/package-name] Short description
    
    Long description
    

    If you have questions about how to write the short / long descriptions, please read these blog articles: How to Write a Commit Message, 5 Useful Tips For A Better Commit Message. Both of them are excellent resources for learning how to write a well-crafted git commit message. If your commit references one or more GitHub issues, always end your commit message body with See #1234 or Fixes #1234 (replace 1234 with the desired GitHub issue ID).

  5. GPG signing your changes is a good idea, but not mandatory.

  6. Push your changes to your branch in your fork, and then submit a pull request agains this repository.

  7. Comment in the pull request when you are ready for the changes to be reviewed: PR ready for review.

At this point you are waiting for my feedbacks. I look at pull requests within few days. I may suggest some improvements or alternatives.

ineluctable-overlay's People

Contributors

bpinto avatar dr-terrible avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

ineluctable-overlay's Issues

gechi-overlay alias

When upgrading gcc to 6.4, I have seen this warning:

* Switching native-compiler to x86_64-pc-linux-gnu-6.4.0 ...!!! Section 'gechi-overlay' in repos.conf has name different from repository name 'ineluctable-overlay' set inside repository

The only reference to this name on the code was on the layout file: aliases = gechi-overlay.

Do you know why I am receiving this warning if this is only an alias?

[x11-misc/polybar] failures on newest release

Hey @Dr-Terrible how are you doing? You've been away for a while!

Couldn't compile this latest version:

/var/tmp/portage/x11-misc/polybar-3.0.6_pre20171018/work/polybar-5737156ae5ea1b179032609dac29d3e60f0773c2/lib/i3ipcpp/src/ipc.cpp: In lambda function:
/var/tmp/portage/x11-misc/polybar-3.0.6_pre20171018/work/polybar-5737156ae5ea1b179032609dac29d3e60f0773c2/lib/i3ipcpp/src/ipc.cpp:25:17: error: ‘Reader’ is deprecated: Use CharReader and CharReaderBuilder instead [-Werror=deprecated-declarations]
   Json::Reader  reader; \
                 ^
/var/tmp/portage/x11-misc/polybar-3.0.6_pre20171018/work/polybar-5737156ae5ea1b179032609dac29d3e60f0773c2/lib/i3ipcpp/src/ipc.cpp:280:4: note: in expansion of macro ‘IPC_JSON_READ’
    IPC_JSON_READ(root);
    ^
In file included from /usr/include/jsoncpp/json/json.h:11:0,
                 from /var/tmp/portage/x11-misc/polybar-3.0.6_pre20171018/work/polybar-5737156ae5ea1b179032609dac29d3e60f0773c2/lib/i3ipcpp/src/ipc.cpp:6:

ideas?

Polybar (Lemonbuddy)

Hey, thanks for the overlay!

Lemonbuddy has been renamed to polybar and the ebuild does not work anymore.

It also requires gcc newer than 5.1, how can I install it along with latest unmasked 4.x version?

[x11-misc/polybar] (v2.5.2) error: 'map' does not name a type

MAKEOPTS="-j1" USE="-* xrender python_targets_python2_7" emerge -1av --nodeps --quiet-build n --fail-clean n ~x11-misc/polybar-2.5.2 produces the following compilation error:

[ 54%] Building CXX object bin/CMakeFiles/polybar.dir/utils/bspwm.cpp.o
cd /var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2_build/bin && /usr/bin/x86_64-pc-linux-gnu-g++   -I/usr/include/freetype2 -I/var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/include -I/var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/lib/concurrentqueue/include -I/var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2_build/bin -I/var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/lib/xpp/include   -DNDEBUG -march=native -O2 -pipe -ftracer -frecord-gcc-switches -fno-stack-protector  -Wabi -fabi-version=8  -w -Wno-all -Wno-dev  -ffunction-sections -fdata-sections  -g0 -Wall -Wextra -Werror -O2 -pedantic -pedantic-errors   -pthread -std=c++14 -o CMakeFiles/polybar.dir/utils/bspwm.cpp.o -c /var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/src/utils/bspwm.cpp
In file included from /var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/src/utils/bspwm.cpp:6:0:
/var/tmp/portage/x11-misc/polybar-2.5.2-r1/work/polybar-2.5.2/include/x11/connection.hpp:185:3: error: 'map' does not name a type
   map<uint8_t, Visual*> m_visual;

Most probably it's an upstream bug due to ambiguous C++ API namespaces.

[x11-misc/polybar] (v3.0.3) error: 'render_util' has not been declared

MAKEOPTS="-j1" USE="-* xrender python_targets_python2_7" emerge -1av --nodeps --quiet-build n --fail-clean n ~x11-misc/polybar-3.0.3 produces the following compilation error:

[ 76%] Building CXX object bin/CMakeFiles/polybar.dir/x11/connection.cpp.o
cd /var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3_build/bin && /usr/bin/x86_64-pc-linux-gnu-g++   -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/include -I/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/lib/concurrentqueue/include -I/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/lib/xpp/include   -DNDEBUG -O2 -pipe -ftracer -frecord-gcc-switches -fno-stack-protector  -Wabi -fabi-version=8  -w -Wno-all -Wno-dev  -ffunction-sections -fdata-sections  -g0 -Wall -Wextra -Werror -O2 -pedantic -pedantic-errors   -pthread -std=c++14 -o CMakeFiles/polybar.dir/x11/connection.cpp.o -c /var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/src/x11/connection.cpp
/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/src/x11/connection.cpp: In constructor 'polybar::v2_0_0::connection::connection(xcb_connection_t*, int)':
/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3/src/x11/connection.cpp:45:3: error: 'render_util' has not been declared
   render_util::query_extension(*this);
   ^
make[2]: *** [bin/CMakeFiles/polybar.dir/build.make:1311: bin/CMakeFiles/polybar.dir/x11/connection.cpp.o] Error 1
make[2]: Leaving directory '/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3_build'
make[1]: *** [CMakeFiles/Makefile2:457: bin/CMakeFiles/polybar.dir/all] Error 2
make[1]: Leaving directory '/var/tmp/portage/x11-misc/polybar-3.0.3-r1/work/polybar-3.0.3_build'
make: *** [Makefile:128: all] Error 2

This bug is related to #15 and most probably is an upstream bug due to ambiguous C++ API namespaces.

ebuild update to 3.10?

Can you update the Torque3D ebuild to support the current release 3.10 as the ebuild is designed for 3.5.1?
asking for a friend btw

repos.conf support

Instead of using layman (another dependency), I prefer to manage external overlays manually editing repos.conf myself.

There is however a dependency in a secondary overlay, dlang, for this overlay, is it necessary?

=== Sync completed for ineluctable-overlay
Unavailable repository 'dlang' referenced by masters entry in '/usr/local/overlay/ineluctable/metadata/layout.conf'
[ineluctable-overlay]
location = /usr/local/overlay/ineluctable
sync-type = git
sync-uri = https://github.com/Dr-Terrible/ineluctable-overlay.git
auto-sync = yes

Dropbox

Do we need to have net-misc/dropbox on this repo? Gentoo's portage has newer versions already.

Split up unmaintained ebuilds into separate overlays

To avoid cluttering this repository, all the ebuilds about abandoned/unmaintained packages should be moved into a separate overlay (the place where ebuilds go to die): https://github.com/Dr-Terrible/graveyard-overlay

Let's trim the fat!

  • dev-util/flint
  • x11-base/xynth
  • dev-ruby/feedzirra
  • dev-ruby/god
  • dev-ruby/gorillib
  • dev-ruby/loofah
  • dev-ruby/sax-machine
  • dev-ruby/certificate_authority
  • dev-python/django-fields
  • dev-python/django-haystack
  • dev-python/django-muddle-users
  • dev-python/django-object-log
  • dev-python/django-object-permissions
  • dev-python/ganeti-webmgr-layout
  • dev-python/inflection
  • dev-python/muddle
  • dev-python/ordereddict
  • dev-python/plugnplay
  • dev-python/smartypants
  • app-editors/atom-bin
  • www-servers/mongrel
  • www-servers/wsgid
  • app-doc/dexy (and all its dependencies)

Games that should be moved into the games-overlay:

  • games-strategy/wesnoth (mostly fixes)
  • games-strategy/ufo-ai
  • games-strategy/endless-sky
  • games-rpg/flare

Polybar: wrong dependency

Polybar depends on x11-proto/xcb-proto, while in Gentoo this package resides in x11-base category.

[Question] Custom shortcut on Termite

Termite has builtin shortcuts but they are set on compilation time and are hard coded.

Is there any way you can think of that would allows us to apply a custom patch that I have on my computer while reusing the ebuild from your overlay in car I want to modify the shortcuts?

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.