Which versions of Perl does LedgerSMB support?

ehu — Sun, 04 Sep 2016 15:03:24 +0000

Which versions of Perl does LedgerSMB support? ehu Sun, 09/04/2016 - 08:03

The table below lists the compatibility of LedgerSMB versions with Perl versions. Products for which support has ceased due to End-of-Life date being reached are not listed and should not be used.

**Perl compatibility**
Perl	1.9 (End-of-Life)	1.10	1.11
5.22	no	no	no
5.24	yes	no	no
5.26	yes	no	no
5.28	yes	no	no
5.30	yes	no	no
5.32	yes	yes	yes
5.34	yes	yes	yes
5.36	yes	yes	yes
5.38	yes	yes	yes
5.40	yes	yes	yes

Versions 1.8 and earlier are not in this table due to the fact that they're past End of Life.

Release

FAQ Category

Which versions of PostgreSQL does LedgerSMB support?

Chris Travers — Thu, 14 Dec 2006 00:52:45 +0000

Which versions of PostgreSQL does LedgerSMB support? Chris Travers Wed, 12/13/2006 - 16:52

The table below lists the compatibility of LedgerSMB versions with PostgreSQL versions. Products for which support has ceased due to End-of-Life date being reached are not listed and should not be used.

**PostgreSQL compatibility**
PostgreSQL	1.9 (End-of-Life)	1.10	1.11
9.3	no	no	no
9.4	no	no	no
9.5	no	no	no
9.6	no	no	no
10	yes	no	no
11	yes	no	no
12	yes	no	no
13	yes	yes	yes
14	1.9.16+	yes	yes
15	1.9.16+	yes	yes
16	1.9.16+	yes	yes

Versions 1.8 and earlier are not in this table due to the fact that they're past End of Life.

Release

FAQ Category

Topic

Which versions do you support?

ehu — Sun, 30 Dec 2012 11:17:51 +0000

Which versions do you support? ehu Sun, 12/30/2012 - 03:17

Active support

Versions 1.10 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:

1.10: Planned End-of-life date: 2024-10-08 (released 2022-10-08)

End of life

If you're looking for help on how to use EOL-ed versions, please try mailing the users mailing list.
If you're looking for someone to create bugfixes, please check with one of the parties providing commercial support or for less urgent fixes LedgerS MB Issues

Version 1.9 has been declared end-of-life on 2023-09-24. The last release in the series is 1.9.30. No futher releases will be made by the community.

Version 1.8 has been declared end-of-life on 2022-09-04. The last release in the series is 1.8.31. No futher releases will be made by the community.

Version 1.7 has been declared end-of-life on 2022-10-04. The last release in the series is 1.7.41. No further releases will be made by the community.

Version 1.6 has been declared end-of-life on 2021-06-10. The last release in the series is 1.6.33. No further releases will be made by the community.

Version 1.5 has been declared end-of-life on 2019-12-23. The last release in the series is 1.5.30. No further releases will be made by the community.

Version 1.4 has been declared end-fo-life on 2017-09-16. The last release in the series is 1.4.42. No further releases will be made by the community.

Version 1.3 has been declared end-of-life on 2015-12-23. The last release in the series is 1.3.47. No further releases will be made by the community.

LedgerSMB versions 1.0, 1.1 and 1.2 won't be maintained any further due to the fact that there are some known security issues which can't be fixed.

Release

FAQ Category

Topic

Open Source ERP: accounting, invoicing and more

Chris Travers — Sun, 18 Mar 2007 06:08:41 +0000

Open Source ERP: accounting, invoicing and more

Mission

The LedgerSMB project provides small and mid-size businesses with solid open source accounting software: integrating invoicing, order processing, quotations and more (ERP). LedgerSMB aims to provide a strong (multi-currency accounting) basis to build your business on -- without vendor lock-in.

The project team considers correctness and performance equally important key usability features and is dedicated to providing both, even on the biggest data sets.

Features

Sales (Invoices, Orders, Quotations)
Receivables & Payables
General ledger
Inventory management
Fixed asset accounting & depreciation
Profit & cost centers, departments, projects
Output documents in PDF, HTML, CSV, Office formats
Mail documents (e.g. invoices) from within the application
Translatable to your language (comes with 45 languages)
and more

The fact that LedgerSMB is open source - meaning that the source code is freely available - makes it even more customizable and flexible.

Use-cases

By company size

Company size is measured by its data and data growth. There are companies known to run with these numbers (as per April 2023):

Transactions and invoices: 650 000 accumulated, growing over 50 000 per month
Journal lines (across invoices and general journal): 2.3 million accumulated, growing over 170 000 per month
Customers and vendors: 260 000
Products: 40 000 configured products with inventory tracking

Most installations are much smaller (50 to 500 transactions per month). Many of the more complex features required for larger companies remain hidden until explicitly configured. This way the software stays simple for smaller, less demanding companies.

By industry

While LedgerSMB will generally work in any industry for its basic accounting functionalities, it is known to have been deployed in the following types of businesses:

Communications
e.g. VOIP services
Factoring
i.e. invoicing of others
(IT) Services
e.g. Website design, IT Support, hourly services
Financial services
e.g. Investment firms
Rental
e.g. Housing rental, IT Hosting
Retail
e.g. Sewing necessities
Trade
e.g. Trading pet foods

Many of these applications include integration with domain-specific applications to perform specific business functions.

Next to the ones listed above, various manufacturing setups have been deployed, ranging from standard (batch based) mass production, to make-to-order one-time product configurations. The latter being supported by a custom developed product configuration plugin.

By country

Although the nature of open source projects makes it hard to know where our software is being used; however, the project is aware of installations in the Australia, Barbados, Canada, Colombia, Denmark, Estonia, European Union, Hong Kong, Hungary, Indonesia, Malaysia, Myanmar, Netherlands, Norway, Philippines, United Kingdom and United States.

The software can run in a different language for each user. Also: documents (invoices, orders, etc) can be produced in selectable languages, different from the user's language.

Contributions

The project welcomes any and all contributions. With lots of areas which would benefit from more attention, we like to invite newcomers to read our community guidelines and start out simple. Good (and helpful!) starting points are translation contributions as well as reviewing our (beginners) documentation.

Current versions

Our current stable version is 1.10 - initially released on Oct 8, 2022. This release has a wide variety of improvements and code cleanups: it features support for customized workflows, the ability to export document templates from the database, much more flexibility for customization by dependency injection, cleaned up document templates, login.pl & setup.pl being translated based on browser preferences and much more... More details about this release can be found in the release notes. This release will see its End-Of-Life for community support on Oct 8, 2024.

Older versions

Version is 1.9 has been declared End-Of-Life on Sep 24, 2023 (released on Sep 24, 2021). This release has a wide variety of improvements and code cleanups: it features faster loading of the menu, fixed migrations from 1.2, the ability to upload a logo into the database and include it in printed documents and much more... More details about this release can be found in the release notes.

Version is 1.8 has been declared End-Of-Life on Sep 04, 2022 (released on Sep 04, 2020). This release has a wide variety of improvements and code cleanups: it features faster loading of the menu, fixed migrations from 1.2, the ability to upload a logo into the database and include it in printed documents and much more... More details about this release can be found in the release notes.

Version is 1.7 has been declared End-Of-Life on Oct 04, 2022 (released on Oct 04, 2019). This release focusses on improved support for foreign currency transactions, lifting the restriction of a single rate per currency per day; UI improved by showing both the functional and foreign currency amounts. Additionally, a lot of work has been spent on increasing the application stability through more rigorous testing and code cleanup. A full summary of the changes since 1.6 can be found in the release announcement. More details on this release can be found in the release notes.

Version 1.6 has been declared End-Of-Life on 2021, June 10th (released on June 10 2018). With 33 patch releases, we consider this version highly stable. Although there are more patch releases for 1.6 than thee are for 1.5, their size is on average smaller, attesting to the project's promise of delivering increasing software quality.

Version 1.5 has been declared End-Of-Life on 2019, Dec 23rd (released on 2016-12-23). With 30 patch releases, we consider this version highly stable. We believe that the lower number of patch releases over a similar life-span as 1.4 is an indication of better stability of the initial 1.5.0 release. We conclude that the project is delivering on its promise of increasing stability of minor releases.

Version 1.4 has been declared End-Of-Life on 2017, Sep 15th (released on 2014-09-15). With 42 patch releases, we consider this version highly stable.

Version 1.3 has been declared End-Of-Life on 2015, Dec 23rd (released on 2011-10-11). With a total of 48 patch releases since the initial release in October 2011, we consider this version highly stable.

Although their use is highly discouraged for both security reasons and data stability issues, older versions are still available for download. When using LedgerSMB versions 1.2 or earlier, you should to do so in only in a highly restricted network environment, because of known security problems.

It's project policy to provide at least 24 months of community support for every 1.x release series, aiming to have two versions supported at any time.

History

LedgerSMB began in 2006 as a fork of the popular general ledger software package called SQL-Ledger largely written and maintained by Dieter Simader since 1999. Versions 1.2 and earlier are heavily based on SQL-Ledger's code.
As of 1.3 our codebase is quickly moving away from what we inherited.
As of 1.5 our User Interface has moved to Dojo Javascript libraries providing a more dynamic feel.
Some of the improvements that we've made to the code base so far include:

Enhanced security
More reports
Better data integrity controls
More code quality control measures
Major code size reduction while growing functionality
Unit testing Infrastructure to help ensure once an issue is fixed it stays fixed
BDD (headless automated browser) Testing infrastructure
A very large number of tests against both testing frameworks

Travel in our history with Internet Archive and WayBackMachine.

Matrix support request ownership proof: ehuels@gmail.com

Chris Travers Sat, 03/17/2007 - 23:08

How to set up POS so it works with barcode scanner, receipt printer, etc.?

hasorli — Sat, 18 Aug 2012 14:03:53 +0000

How to set up POS so it works with barcode scanner, receipt printer, etc.? hasorli Sat, 08/18/2012 - 07:03

Q: This particular merchant runs Windows. I don't think they have a pole display, though I can check. Ideally, it would be great to accommodate, with or without pole display. If it runs better on Linux, going forward I would propose Linux workstations for new merchants.

Ok. Let's first explain what the problems we have to solve are, then discuss the solutions that are bundled.

In general web browsers are engineered so that malicious sites can't access your computer's hardware. In general we don't want to change the browser (for example with an add-on) to make it do this because there might be a capacity for abuse elsewhere. So things like receipt printers, pole displays, cash drawers, and barcode scanners cannot be directly be accessed by the browser. This makes a web-based point of sale rather challenging, but we have solutions to these problems. The solutions though are only tested on Linux. On Windows they will require slight modification and I would recommend some extra testing. Backup/fallback methods are discussed below as well. What we do instead preferably is to turn the point of sale terminal into a server for the point of sale hardware. Scripts to do this (written in Bash) are in the utils/pos directory of the LedgerSMB installation. the client-side script is pos-hardware-client-startup-script which basically fires up netcat and listens for data to redirect to a hardware port. You probably want to use firewall software to limit this traffic to approved servers. The ports are configurable on both ends. On the LedgerSMB side, see the pos.conf.pl. The other is directnet.pl which is used to send printable documents over this (and to the POS printer on the other side). This is designed to be a low-latency alternative to using CUPS and the like. It redirects pole display logic usually to a serial port, and the printer logic to a parallel port. This means you can use any printer that accepts ESC/POS and it will send signals to open the cash drawer (programmable in the pos.conf.pl) if the cash drawer is the kind that plugs into the printer. You can also use a pole display although currently we only have drivers for the LC3000 by Logic Controls. The drivers are really easy to write though. Feel free to ask for help or contribute one. Barcode scanners and magnetic stripe readers need to come into the computer as keyboard input. Typically this means a keyboard wedge interface for magstripe readers, and either a keyboard interface for a barcode scanner, or a barcode scanner attached to a POS keyboard with a built-in barcode decoder. I have had better luck with the latter in terms of long-term maintenance, but they both work. On to the pos.conf.pl. The default values here are in the pos.conf.pl.template, so please cp pos.conf.pl.template pos.conf.pl For the miost part this defines a single variable for storing the information called $pos_config. Keys for this and their significance are: rem_host: Remote host to send pole display/printer info to. By default this is the remote host. However if you are running X11 applications remotely you may have to change this. pd_host; Host for the pole display. Defaults to rem_host pd_port: Port for the pole display. Defaults to 6601 pd_proto: Protocol for pd. Either 'tcp' or 'udp' defaulting to udp. rp_host rp_port rp_proto Same as pd_* above but for printer rp_cash_open: The code to open the printer. Defaults to those for the Epson U220D iirc, which is binary string of values 27, 112, 0, 25, 250 coa_prefix: prefix for the till amounts. If you have a till '16' and a coa_prefix of 1300, the till account will be 1300.16. This account must exist or you will get errors. close_cash_accno: Cash account to put closing cash into. Must exist by closing time. $pos_sources is used to define memo fields for different types of payment. You can customize this as you want. $pos_source_default is the default for the sources drop down. curren is the currency breakdown covers your currency denominations. Used in closing. I dont know if you want to add a 0.5 as 50 cent piece there since those are rare. till_type is either the 'cashier' meaning the employee id becomes the till number or 'terminal' in which the last octet of the IP address becomes the till number. If you need to customize this handling you can do so underneath the request to stop editing at a certain point. Advanced options include source_accno_override used to override cash account handling of various sources (such as gift certs for example) disable_tables is no longer necessary. But you can use this if you aren't using projects and/or departments. It defaults to disabling everything. If the directnet approach for printing does not work for you you can comment out the printer definition at the bottom of the pos.conf.pl and set up cups to process and send the file to the workstation to be printed. This adds a few seconds often, however, so where directnet works, it is preferred especially in time-critical point of sale environments.

Release

1.3

FAQ Category

Installation

Topic

Obsolete

System requirements

ehu — Sat, 30 Jun 2012 12:58:33 +0000

System requirements

Hardware requirements

The hardware required to run LedgerSMB greatly depends on the number of users. However, with a small number of users (up to 10 or so), a 32bit server with 512MB to 1GB of memory (including Linux Server OS) and just a few hundred MB of storage (excluding OS) should be enough to get good performance.
For a 64bit server, you probably need 1GB to 2GB of memory, but otherwise the requirements are the same.

Operating system requirements

LedgerSMB runs on Linux/Unix (for the Server) and any platform with a compatible Web Browser (for the Client).
Platforms that have known-compatible browsers are Linux, Windows, MacOS, most smart phones and tablets should also work although the current UI requires a large screen for optimum usability. (Minimal size: 9.7" tablet in landscape mode.)

Unix includes all flavours (variants) of Linux including

Debian
Mint
Ubuntu
RedHat
Fedora
BSD
MacOS / OS X
and many more

MS Windows

While in the past the server would run on Windows as well, this is currently not tested and expected to break.
LedgerSMB has a client / server architecture, so while it is often better to run the server on Linux, this will not stop you from running the clients on windows. In fact this is a common situation and is fully supported.

For more information on running on windows please look at the FAQ item Can I use LedgerSMB on MS Windows?

Software requirements (client)

On the client, LedgerSMB requires a compatible browser. As of version 1.9, the development team keeps track of which exact browser capabilities that are used by LedgerSMB to determine which browser versions are supported and which ones are not. On versions 1.8 and older, the indicated minimum requirement is based on the indication provided by the Dojo Toolkit development team in combination with a rough impact estimation of additional capabilities used by LedgerSMB's own JavaScript.

Minimum browser versions supported by LedgerSMB (by version)
	Chrome	Safari		Firefox	Opera	Edge	Internet Explorer
	Chrome	Desktop	Mobile	Firefox	Opera	Edge	Internet Explorer
1.4	13	5		3.6	10.50	(all)	8
1.5							10
1.6
1.7
1.8							n/a
1.9	2017-09 (61)	2017-03 (10.1)	2017-03 (10.3)	2018-05 (60)	2017-09 (48)	2017-10 (16)	n/a
1.10	2017-09 (61)	2017-09 (11)	2017-09 (11)	2018-05 (60)	2017-09 (48)	2020-01 (79)	n/a
1.11	2018-03 (65)	2018-03 (11.1)	2018-03 (11.3)	2018-05 (60)	2018-03 (52)	2020-01 (79)	n/a

Please note that on Android, browsers are being pushed to end-user devices so that most devices always have the latest Chrome, FireFox or Opera browser. To that extent, there's little point in mentioning the oldest supported version. If you would be interested to know anyway: the desktop versions of the same browsers are a good indication of support of the required capabilities on mobile as well.

Explicitly unsupported clients include:

Lynx
w3m
IE9 or earlier

Software requirements (server)

LedgerSMB builds upon technology of some very widely used - proven - projects:

PostgreSQL - the enterprise level quality open source database
Starman (perl webserver)
Perl - the programming language of the web
(Xe)LaTeX - the typesetting language (optional)
This is used by the Templating system to generate PDF and Postscript output for printing, email or saving to disk

Each version of LedgerSMB has its own requirements. The high level requirements are listed in the table below.

Requirements by LedgerSMB version
	Status	PostgreSQL	Application server / HTTP server	Perl	PDF
	Status	PostgreSQL	Application server / HTTP server	Perl	PDF	PDF/A
1.4	End-Of-Life (no community support)	8.4 and up	Apache 1.3 and up	5.10 and up	LaTeX for ASCII or XeLaTeX for UTF-8 characters	LuaTeX with pdfx TeX package
1.5		9.4 and up	Starman*	5.10 and up
1.6				5.14 and up
1.7				5.18 and up
1.8		9.6 and up		5.20 and up
1.9	old stable	10 and up		5.24 and up
1.10	stable	13 and up		5.32 and up	Customizable; default: LaTeX for ASCII or XeLaTeX for UTF-8 characters	Customizable; default: LuaTeX with pdfx TeX package
1.11	preview	13 and up		5.32 and up		Customizable; default: LuaTeX with pdfx TeX package

* While Starman is the prefered (and tested) webserver for 1.5 and newer.
It should ALWAYS be reverse proxied as HTTPS using Apache/Nginx or possibly other HTTP servers.
It may be possible to run directly from another HTTPD server, but this is not a supported configuration.
Also, in most cases there are performance gains to be had by using Starman.

Perl module dependencies

The Perl module dependencies are listed in the 'cpanfile' in the root of the project tree. Many distributions include at least some of the dependencies in their repositories, so that it shouldn't be necessary to install all the dependencies listed in the cpanfile from CPAN.

During the installation process, the availability of the "cpanm" binary is required.

ehu Sat, 06/30/2012 - 05:58

Topic

Installation

1.11 release notes

ehu — Fri, 06 Jan 2023 21:35:30 +0000

1.11 release notes

Be sure to check the UPGRADE NOTES below!

What's new in LedgerSMB 1.11

New features

Feature 1

Description 1.

Note for upgrades: There is no impact on upgrades.

Reclassification of negative (current) assets to liabilities (and vice versa)

In it's common practice to present negative current assets as positive current liabilities. An example where this regularly happens is when a bank current account goes into overdraft: instead of the bank owing money to the company (an asset), the company owes money to the bank (a liability). This release adds a new configuration on the account settings screen: "Negative balance heading". This setting applies to asset and liability accounts.

When the "Negative balance heading" is set, when an asset account has a credit balance, it will be reported as a liability under the heading indicated in this option.

Note for upgrades: Users wanting to use this option need to explicitly set it on affected accounts after migration of the database completes.

Webservices for GIFIs, SICs, Types of Business, Price groups, Warehouses and Languages

Webservices have been created to manage configuration of a number of entities:

Countries (/erp/api/v0/countries)

These were created in support of moving the front-end to Vue3 components, with the intent to use them as a learning experience for further API development. Due to this approach, the services do not support filtering, sorting or paging yet. For more information on how to use these services, see LedgerSMB Webservices.

Note for upgrades: There is no impact on upgrades.

Notable changes

Change summary 1

Explanation 1.

Note for upgrades: There are no consequences for upgrades: template sets used with 1.9 can be carried over without modification.

Upgrade notes

Sequences in System > Sequences switched to show "next value" instead of "last value"

If you use custom sequences, you need to increase the values in the Sequence column by 1 in order to prevent values from being used twice.

Background: The number shown in the "Sequence" column on the System > Sequences menu page, used to show the last value used. As of 1.11, it shows the next value that will be used. This ensures that value "1" in the sequence will be used now (it used to be skipped before), which helps auditability.

ehu Fri, 01/06/2023 - 13:35

Topic

Draft

Can I use the webservices using curl?

ehu — Sun, 13 Jun 2021 20:35:25 +0000

Can I use the webservices using curl?

I'm writing this script in bash that I want to use to invoke functionality in LedgerSMB. Can I use curl and the webservices API to do that?

ehu Sun, 06/13/2021 - 13:35

Yes you can. In order to do so, you must first create a valid session for your follow-up requests by authenticating:

$ curl -c cookie-jar.txt -H 'Content-Type: application/json' \
    -d '{"login": "<your-user>", "password": "<your-password>", "company": "<your-company>"}' \
    https://example.org/login.pl?action=authenticate

The request above creates a file called "cookie-jar.txt" in the current directory which - after successful authentication - contains the authentication cookie to be used for follow-up requests. To use it, use curl's -b parameter:

$ curl -b cookie-jar.txt -c cookie-jar.txt -H 'Content-Type: application/json' \
    -d @request-body.json https://example.org/erp/api/v0/invoices/

Note that the use of curl's "-d" parameter implies that a POST request is issued. The presence of the at-sign in "@request-body.json" tells curl to read the request body from the file 'request-body.json'. When you decide not to use 'curl', but issue these requests from programming language, please make sure to issue POST requests.

OpenAPI documentation of the LedgerSMB API by version is available at https://docs.ledgersmb.org/openapi

Component

Base

Release

1.9

1.10

FAQ Category

Integration

Chat Support (Matrix)

Anonymous — Wed, 26 Dec 2012 19:21:35 +0000

Chat Support (Matrix)

For real-time help try our Matrix (IRC like) room #ledgersmb - you will usually find most of the core team hanging out there. The most feature-full and commonly used client is Element. It is available as a web client (for computers) and also as Android and iOS clients from within the appropriate app stores. We suggest you create a matrix account as that will allow you to log back in later to see our response to your question.

There are people there who range from users to developers who are willing to help. We have agreed to adopt the Ubuntu code of conduct for our community. Please read it if you plan on joining.

Please keep in mind that the community (especially the people you may need help from) are scattered around the world and will likely be in a different timezone to you. This means that it can sometimes take quite a few hours before someone responds. (although these days on IRC there is someone around almost all of the time). For email lists this is not a big problem, but if you are using Matrix (directly or via a matrix guest session) you will need to stay connected until someone answers otherwise we have no way to contact you :-)

If you ask for help as a signed up Matrix user, please log back in and check for a response occasionally, we will always respond as soon as someone is available.

NOTE: there is a nice feature of the Riot web app (a bell shaped icon near the top right) that shows all the messages that mention your name.
This is useful when you come back after a while to see if someone has responded to your question.
Just click on a message there to jump to that point in the chat history

Connecting to MATRIX

Read more about using Matrix and Element Client

Webclient

You can use a browser-based matrix client to join the channel.
It defaults to guest access with reduced features, but it is trivial to sign up and get additional benefits like channel history and other things.

Dedicated Chat client

Anonymous (not verified) Wed, 12/26/2012 - 11:21

Topic

Operating system

RedHat Enterprise Linux

Release

FAQ Category

Download

Anonymous — Sat, 01 Apr 2017 12:28:25 +0000

Download

Maintained releases

The current stable release line is 1.10. For more information about older versions, see the FAQ item about supported releases. Versions 1.6 and older should no longer be used due to known security issues that will not be resolved in that code base.

Official release distribution

The latest official release of LedgerSMB is always at download site. Releases are signed with GPG to assert integrity. Our public GPG key can be found on MIT's key server or on pgpkeys.eu. Install and upgrade info.

You can verify the release with the command

$ gpg --verify ledgersmb-<version>.tar.gz.asc ledgersmb-<version>.tar.gz

Docker images

There are production level Docker images available on GitHub. New containers are released on every stable (1.10) and old-stable (1.9) release. Docker images are around 250MB in size.

The docker repository identifier is "ledgersmb/ledgersmb" with the "latest" tag always pointing to the most recent stable release, which is currently the most recent 1.10.x release. The "master" tag points to the most recent alpha or beta of the development version (1.11).

Distribution packages

A Debian package is available in Debian v11 (stable, 'bullseye') and Debian v10 (oldstable, 'buster') but was not available in Debian v9 (Stretch, oldoldstable) due to problems with the Dojo dependency (which failed to build). Note that the current LedgerSMB version that is recommended for use is one in the 1.10.x series, which is not in Debian. We're working to get 1.8.x or 1.9.x packages into Debian.

Newer packages than those distributed by Debian can be found in the LedgerSMB APT repository (along with their updated dependancies as necessary).

Ubuntu packages are available in the standard distributions based off of the Debian packages.

Newer packages than those distributed in Ubuntu can be found in the LedgerSMB PPA repository.

RPM Packaging contributions solicited.

FreeBSD Packaging contributions solicited

OpenBSD Packaging contributions solicited.

Virtual Box No up-to-date images at this time.

Keeping up with the latest developments

The latest 1.9.x and 1.10.x are available directly from GitHub as a .zip file (it's not an official release, but has the latest fixes you may need) 1.9.x from GitHub, 1.10.x from GitHub. Check the repository for the change log in 1.10.x from GitHub or the changes in bleeding edge ('master').

LedgerSMB public GPG key
The LedgerSMB GPG public key can be found on the MIT key server. Here is the direct link.

Anonymous (not verified) Sat, 04/01/2017 - 05:28

Topic

Operating system