Categories
PHP

svn status codes

svn status [PATH…]

The first seven columns in the output are each one character wide, and each column gives you information about a different aspect of each working copy item.

For each updated item a line will start with a character reporting the action taken. These characters have the following meaning:

  • U: Working file was updated
  • G: Changes on the repo were automatically merged into the working copy
  • M: Working copy is modified
  • C: This file conflicts with the version in the repo
  • ?: This file is not under version control
  • !: This file is under version control but is missing or incomplete
  • A: This file will be added to version control (after commit)
  • A+: This file will be moved (after commit)
  • D: This file will be deleted (after commit)
  • S: This signifies that the file or directory has been switched from the path of the rest of the working copy (using svn switch) to a branch
  • I: Ignored
  • X: External definition
  • ~: Type changed
  • R: This file got replaced. / Item has been replaced in your working copy. This means the file was scheduled for deletion, and then a new file with the same name was scheduled for addition in its place.
  • E: Existed

A character in the first column signifies an update to the actual file, while updates to the file’s props are shown in the second column.

'Coz sharing is caring
Categories
linux Microsoft

What are .deb, .rpm and .msi?


Files such as .deb and .rpm are more akin to a .zip file. They’re a directory tree of files and sub-directories that contain files related to a particular application and/or library of files.

Distros

The .deb files are meant for distributions of Linux that derive from Debian (Ubuntu, Linux Mint, etc.). The .rpm files are used primarily by distributions that derive from Redhat based distros (Fedora, CentOS, RHEL) as well as by the openSuSE distro.

What’s special about them?

These files have one other special trait that sets them apart from .zip files, in that they can include a specification that contains rules that tell the package manager software running on a system that’s installing one of these files to do additional tasks. These tasks would include things such as:

  • creating user accounts on the system
  • creating/modifying configuration files that aren’t actually contained in the .deb or .rpm file
  • set ownership/permissions on the files after installation
  • run commands as root on the system that’s installing the package
  • dependencies, both formats can include names or packages and/or service names that they require to be present on a system, prior to installation.

What about .msi files?

.msi files are similar to .deb & .rpm files but likely even more sophisticated. The .msi files are utilized by the Windows Installer and offer additional features such as:

  • GUI Framework
  • generation of uninstall sequences
  • A framework within itself – for use by 3rd party installers
  • Rollbacks
  • Advertisement
  • User Interface
  • etc.

I’d suggest taking a look at the various Wikipedia pages on these subjects if you want a more in-depth explanation.

References

'Coz sharing is caring