* J.C. Roberts wrote:
A better answer is to replace the commercial unarj uncompressor with the
free, open source compressor/uncompressor available here:
http://arj.sourceforge.net/
I'll do the work, but tell me which way you want to go.
If there is a functional and free unarj, then I
On Thu, Jan 11, 2007 at 10:45:32PM +0100, Marc Balmer wrote:
* Joachim Schipper wrote:
On Thu, Jan 11, 2007 at 02:23:22PM +0100, Antoine Jacoutot wrote:
On Thu, 11 Jan 2007, Lars Olsson wrote:
with arj 3.14a that was able to open in OpenBSD. Conclusion: Remove
unarj from the ports
* Joachim Schipper wrote:
On Thu, Jan 11, 2007 at 10:45:32PM +0100, Marc Balmer wrote:
* Joachim Schipper wrote:
On Thu, Jan 11, 2007 at 02:23:22PM +0100, Antoine Jacoutot wrote:
On Thu, 11 Jan 2007, Lars Olsson wrote:
with arj 3.14a that was able to open in OpenBSD. Conclusion:
code used/downloaded in our ports tree is just a repackaging
of the source that came with the windows self-extractor. I've diffed
the stuff we use against the current source from the win32
self-extractor and there only a handful of differences, so fixing the
unarj port is not a big deal
On Thu, 11 Jan 2007, Lars Olsson wrote:
with arj 3.14a that was able to open in OpenBSD. Conclusion: Remove
unarj from the ports tree because it doesn't work anyway.
Can't it be updated?
--
Antoine
On Thu, Jan 11, 2007 at 02:23:22PM +0100, Antoine Jacoutot wrote:
On Thu, 11 Jan 2007, Lars Olsson wrote:
with arj 3.14a that was able to open in OpenBSD. Conclusion: Remove
unarj from the ports tree because it doesn't work anyway.
Can't it be updated?
Even if it cannot be, arj is mostly a
* Joachim Schipper wrote:
On Thu, Jan 11, 2007 at 02:23:22PM +0100, Antoine Jacoutot wrote:
On Thu, 11 Jan 2007, Lars Olsson wrote:
with arj 3.14a that was able to open in OpenBSD. Conclusion: Remove
unarj from the ports tree because it doesn't work anyway.
Can't it be updated?
