![]() ![]() etc/apt/sources.list:deb wily-security main restricted etc/apt/sources.list:deb wily-backports main restricted universe multiverse etc/apt/sources.list:deb wily-updates multiverse etc/apt/sources.list:deb wily multiverse etc/apt/sources.list:deb wily-updates universe etc/apt/sources.list:deb wily-updates main restricted Unless there are files that shouldn't be there, the output will be the same.Īn example output on my machine would be this: /etc/apt/sources.list:deb wily main restricted If you want a shorter but possibly only in 99.9% of all cases correct output that may search too much files (includes all /etc/apt/sources.list* files and directories, not only /etc/apt/sources.list and `/etc/apt//*), you could also use this: grep -r -include '*.list' '^deb ' /etc/apt/sources.list* no *.list.save files used for backup or others with illegal names. It searches really only all *.list files that will be parsed by apt, but e.g. This excludes commented lines as well as deb-src lines to enable source code repositories. I am surprised that the simplest but most effective way to get all enabled binary software sources together with the file they're specified in hasn't been posted yet: grep -r -include '*.list' '^deb ' /etc/apt/sources.list /etc/apt//įrom all processed files, this will print every line starting with deb. I needed a question on superuser to figure out the correct regex. Grep -Po "(? installppas.sh on the source machine, then run the contents of installppas.sh on the destination machine. # Script to get all the PPAs which are installed on a system Next stop: do that for the other repositories: When you call it with listppas > installppas.sh you get an installppas.sh script you can copy onto a new machine to reinstall all PPAs. Grep -o "^deb \ /\ " $APT \Įcho sudo apt-add-repository ppa:$USER/$PPA ![]() # listppas Script to get all the PPAs installed on a system ready to share forįor APT in `find /etc/apt/ -name \*.list` do With a little cleanup I got a script that lists the PPAs, but not any other repository: More packaging options are described in our wiki.Thanks for the pointers. The creation of a TGZ file for Linux/Unix (produced in build/distributions). The creation of an EXE file for Windows (produced in build/launch4j). This can be solved by executing: sudo xattr -r -d /Applications/muCommander.app Note: as the application is not signed, the following error may appear when trying to start is on macOS: "muCommander damaged and cannot be opened". The creation of a DMG file for MAC OS (produced in build/distributions). Then, you can run a debugger that connects to this port using your favorite IDE (see an example for doing this with IntelliJ). In order to debug muCommander, you first need to configure a port using an environment variable named DEBUG (e.g., 5005). It is recommended that whenever you get unclear compilation error and before submitting your change you do. The following commands can be invoked from the root directory of the repositoring with no further installation. The use of Gradle wrapper significantly simplifies the build from the command line. By importing the main project that is located at the root directory of the repository you will get all the required code in the IDE. Most of the popular IDEs today allow you to import Gradle projects out-of-the-box or via an IDE plugin. ![]() The code repository of muCommander is comprised of a main project that contains its core functionality and several sub-projects. Code EditingĪfter cloning the source code repository from GitHub, you would probably want to import the project to an Integrated Development Environment (IDE) such as Eclipse or IntelliJ. Within pull requests it is possible to review, discuss and improve the changes until they are ready for production. If you would like to contribute code, it is required to fork the repository and submit a pull request. If you want to get involved in muCommander or have any question or issue to discuss, you are more than welcome to join our rooms on Gitter. If you happen to speak a language that muCommander is not available in or able to improve existing tranlations, you can help translate the interface using the zanata platform.See the next section for tips for developing muCommander. Want to fix a bug or implement a feature? We are using the standard GitHub flow: fork, make the changes and submit a pull request.Found a bug or thinking about a useful feature that is missing? File an issue.There are several ways to contribute to muCommander: It runs on any operating system with Java support (macOS, Windows, Linux, *BSD, Solaris.). MuCommander is a lightweight, cross-platform file manager with a dual-pane interface. ![]()
0 Comments
Leave a Reply. |