Contributed by jose on from the cvs-replacement dept.
A port of Subversion to OpenBSD has been put on hold because of the required dependencies (they break other things), but it should be possible to build it manually.
(Comments are closed)
OpenBSD Journal
Contributed by jose on from the cvs-replacement dept.
A port of Subversion to OpenBSD has been put on hold because of the required dependencies (they break other things), but it should be possible to build it manually.
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By Anonymous Coward () on
What things ?
And where is the port ? Or is there some draft available ?
Comments
By Anonymous Coward () on
Comments
By pixel fairy () on
Comments
By apache-department () on
Comments
By Anonymous Coward () on
And so the port is on hold because an apache2 port
wasn't done/commited yet, is it not ?
Or maybe there was no clue that apache2 was needed, therefore is "on hold".
So jose, is it still on hold because it breaks things ? What does it break after all ? Please
document yourself before doing such posts.
Comments
By Srebrenko Sehic () haver@insecure.dk on mailto:haver@insecure.dk
By Anonymous Coward () on
By jose () on http://monkey.org/~jose/
By Karel Gardas () kgardas@NO_SPAMobjectsecurity.com on mailto:kgardas@NO_SPAMobjectsecurity.com
Cheers,
Karel
Comments
By Janne Johansson () on
inability to state where Arch is "expensive" in
comparison to other versioning systems. It is sort
of impossible to have a system which is optimal in
all cases, and the cases where the common versioning
systems in use today have their problems are mostly
known so that you may select one based on what type
of use you will experience. When asked, the Arch
guy couldn't answer, leading many people (including me)
to believe that he hasn't researched it enough.
This in turn might lead to conclusions about the
overall quality of Arch in itself. Perhaps not true
and correct conclusions, but you know how people
are... First impressions kind of lasts.
When choosing between 3DES and Blowfish for your
ssh, you can make a decision based on if you want
speed or extra security, but if one of the cryptos
were marked (only by the coder) as best in all
possible cases, some people will tend to disbelieve
such claims straight away.
I am FULLY aware of that I can't either prove nor
disprove anything on how Arch actually performs in
regard to branching, tagging, storing efficiently
and all other factors that versioning systems face,
but I do know that I was dissapointed when he wouldn't
state any "facts" on which direction Arch had chosen
to optimise for, and what the consequences would be
based on that decision. Systems (filesystems, VM
systems, databases and so on) always optimise for
speed or space or time or some other factor, and
almost every time as a tradeoff for something else.
I wouldn't want to import a large project from a
known versioning system into Arch just to be the
first to find out that it starts to suck when some
part of it (the diff-list, whatever) is 1% over my
internal memory or some weird factor like that.
Suddenly I'm "stuck" with a system that requires me
to buy more memory or switch machine just when the
system started to grow largish, meaning that I'm
growing INTO the current VS. Sure, this might happen
to all VS'es, but sometimes you need to play it
safe if you expect to have your project grow.
And to play it safe sometimes means to disregard
notions of "new and all-improved systems" that claim
to have no negative parts at all.
Of course, all this might be provably wrong, perhaps
the Arch website has all the info, perhaps someone
has tested Gbyte historyfiles, but the impression
I got THEN lead me to this decision. Informed persons
may enlighten me (and us all!) at any time. =)