Always private
DuckDuckGo never tracks your searches.
Learn More
You can hide this reminder in Search Settings
All regions
Argentina
Australia
Austria
Belgium (fr)
Belgium (nl)
Brazil
Bulgaria
Canada (en)
Canada (fr)
Catalonia
Chile
China
Colombia
Croatia
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hong Kong
Hungary
Iceland
India (en)
Indonesia (en)
Ireland
Israel (en)
Italy
Japan
Korea
Latvia
Lithuania
Malaysia (en)
Mexico
Netherlands
New Zealand
Norway
Pakistan (en)
Peru
Philippines (en)
Poland
Portugal
Romania
Russia
Saudi Arabia
Singapore
Slovakia
Slovenia
South Africa
Spain (ca)
Spain (es)
Sweden
Switzerland (de)
Switzerland (fr)
Taiwan
Thailand (en)
Turkey
Ukraine
United Kingdom
US (English)
US (Spanish)
Vietnam (en)
Safe search: moderate
Strict
Moderate
Off
Any time
Any time
Past day
Past week
Past month
Past year
  1. freelancer.in

    Job Description: I am looking for an experienced Linux Administrator who is familiar with creating Linux Packages (RPMs, DEBs etc) and creating systemd units/init scripts for existing software. Please reply with your experience and the URL for an existing RPM/DEB that you have packaged in a public repo. Skills: Debian, Linux, Red Hat, Ubuntu
  2. unix.stackexchange.com

    To correct you on Debian packaging, the debian directory exists in the directory into which the upstream source was extracted into, and Debian does value the concept of a pristine upstream source tarball very much. When a source package is built, there are three (two for native packages) files that together are called the source package: the ...
  3. Minimum 1 year of experience with Linux (Red Hat or Debian) Knowledge of software development lifecycle, including QA and deployments; Good written and verbal communication skills, with attention to detail; The following are considered a plus. Experience building RPM packages or Debian packages
  4. linuxsimply.com

    Nov 23, 2023DEB and RPM are the two popular package managers that are mainly used by Debian and RedHat-based Linux distributions respectively. If you understand the differences between the two packages then you will be able to manage the software effectively. I will thoroughly discuss deb vs rpm in this article. You can learn how to distinguish between these two well-known package managers from this writing.
  5. linkedin.com

    Posted 1:10:36 AM. Canonical is a leading provider of open source software and operating systems to the global…See this and similar jobs on LinkedIn.
  6. JOB DESCRIPTION. We have an exciting and rewarding opportunity for you to take your software engineering career to the next level. As a Software Engineer III at JPMorgan Chase within the Corporate Sector on the Workforce Technology team, you serve as a seasoned member of an agile team to design and deliver trusted market-leading technology products in a secure, stable, and scalable way.
  7. There isn't much point in packaging software for multiple formats. In addition, developers usually don't package their software in deb/rpm/pacman formats. They publish the source code with build instructions and distributions package the software. There is no need for the devs to build different formats for different package managers.
  8. Packaging Engineer jobs in Columbus, OH. Sort by: relevance - date. 25+ jobs. Quality Engineer. Urgently hiring. Axium Packaging 3.2. ... Knowledge or experience using 2D CAD Software; Mechanical or Industrial Engineering Degree or similar. This Job Is Ideal for Someone Who Is: Dependable -- more reliable than spontaneous ...
  9. stackoverflow.com

    Generic issues. Your way to package your stuff (with dependent libs) to /opt is how proprietary (and even open-source) software is packaged. It's recommended practice of The Linux Foundation (see my answer to the other question for links).. External libs may be either compiled from scratch and embedded into your build process as a separate step (especially if you modify them), or fetched from ...
  10. Can’t find what you’re looking for?

    Help us improve DuckDuckGo searches with your feedback

  1. A lot of people compare installing software with apt-get to rpm -i, and therefore say DEB better. This however has nothing to do with the DEB file format. The real comparison is dpkg vs rpm and aptitude/apt-* vs zypper/yum.

    From a user's point of view, there isn't much of a difference in these tools. The RPM and DEB formats are both just archive files, with some metadata attached to them. They are both equally arcane, have hardcoded install paths (yuck!) and only differ in subtle details. Both dpkg -i and rpm -i have no way of figuring out how to install dependencies, except if they happen to be specified on the command line.

    On top of these tools, there is repository management in the form of apt-... or zypper/yum. These tools download repositories, track all metadata and automate the downloading of dependencies. The final installation of each single package is handed over to the low-level tools.

    For a long time, apt-get has been superior in processing the enormous amount of metadata really fast while yum would take ages to do it. RPM also suffered from sites like rpmfind where you would find 10+ incompatible packages for different distributions. Apt completely hid this problem for DEB packages because all packages got installed from the same source.

    In my opinion, zypper has really closed the gap to apt and there is no reason to be ashamed of using an RPM-based distribution these days. It's just as good if not easier to use with the openSUSE build service at hand for a huge compatible package index.

    --vdboor

    Was this helpful?
Custom date rangeX