-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
1261 lines (1158 loc) · 53 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html class="no-js" lang="">
<head>
<meta charset="utf-8">
<meta http-equiv="x-ua-compatible" content="ie=edge">
<title></title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="apple-touch-icon" href="apple-touch-icon.png">
<!-- Place favicon.ico in the root directory -->
<!-- Font -->
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,700,600italic,700italic,800,800italic' rel='stylesheet' type='text/css'>
<link href='https://fonts.googleapis.com/css?family=Montserrat:400,700' rel='stylesheet' type='text/css'>
<!-- Font -->
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" href="css/main.css">
<link rel="stylesheet" href="css/font-awesome.min.css">
<link rel="stylesheet" href="css/font-tech.css">
<link rel="stylesheet" href="css/animate.css">
<link rel="stylesheet" href="css/bootstrap.min.css">
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="css/responsive.css">
<script src="js/vendor/modernizr-2.8.3.min.js"></script>
</head>
<body>
<!--[if lt IE 8]>
<p class="browserupgrade">You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> to improve your experience.</p>
<![endif]-->
<!-- Header Start -->
<header id="home">
<!-- Main Menu Start -->
<div class="main-menu">
<div class="navbar-wrapper">
<div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-collapse collapse">
<ul class="nav navbar-nav navbar-right">
<li><a href="#about">About</a></li>
<li><a href="#platforms">Platforms</a></li>
<li><a href="http://www.ravenports.com/catalog">Catalog</a></li>
<li><a href="#quickstart">QuickStart</a></li>
<li><a href="#schedule">Schedule</a></li>
<li><a href="#contributing">Contributing</a></li>
<li><a href="#news">News</a></li>
<li><a href="#features">Services</a></li>
<li><a href="#contact-us">Contact</a></li>
</ul>
</div>
</div>
</div>
</div>
</div>
<!-- Main Menu End -->
<!-- Sider Start -->
<div class="slider">
<div id="fawesome-carousel" class="carousel slide" data-ride="carousel">
<ol class="carousel-indicators indicatior2">
<li data-target="#fawesome-carousel" data-slide-to="0" class="active"></li>
<li data-target="#fawesome-carousel" data-slide-to="1"></li>
<li data-target="#fawesome-carousel" data-slide-to="2"></li>
<li data-target="#fawesome-carousel" data-slide-to="3"></li>
</ol>
<div class="carousel-inner" role="listbox">
<div class="item active">
<img src="img/tech-slider1.jpg" alt="Slider 1: servers">
<div class="carousel-caption">
<h2 class="wow fadeInLeft">Universal *Nix application builder</h1>
</div>
</div>
<div class="item">
<img src="img/tech-slider2.jpg" alt="Slider 2: bits">
<div class="carousel-caption">
<h2 class="wow fadeInLeft">Create master package repositories to exact specifications
without regard to target OS</h1>
</div>
</div>
<div class="item">
<img src="img/tech-slider3d.jpg" alt="Slider 3: hard disk">
<div class="carousel-caption">
<h2 class="wow fadeInLeft">Superior to other frameworks for both users and developers</h1>
</div>
</div>
<div class="item">
<img src="img/raven-slider4a.png" alt="Slider 4: Ravenports logo">
</div>
</div>
</div>
</div>
<!-- Sider End -->
</header>
<!-- Header End -->
<!-- About Section -->
<section id="about" class="site-padding">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>About the <span>Ravenports Universal Package System</span></h3>
</div>
</div>
</div>
</div>
<div class="container single-blog">
<p class="text">
Ravenports is an integrated system designed to build packages of complex
software on all UNIX-like platforms. It is considered “universal” because
Ravenports is not anchored to any single operating system; once the build
procedure for a particular software is created (a.k.a “port”), that
software is then available for all supported platforms. The simplest use case
is to access the freely available prebuilt package repository for each supported
platforms. More complex usage involves customizing builds to create private
package repositories for specialized use. The product packages and repositories are
manipulated with a package manager.<br/><br/>
Notable advantages of Ravenports over other frameworks:
</div>
<div class="container">
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-sliders"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Inherent support of variant packages</h4>
<p>Other frameworks may refer to these as “flavors” or “slave
ports”. A variant package set is one that is built with a
different configuration over the standard set. The use of variant
packages eliminates the need for user-configurable options,
meaning the consumer is likely to have access to a pre-built binary
package and not have to build the software themselves.</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-flag "></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Inherently higher quality build procedures</h4>
<p>Most other frameworks are based on makefiles or shell scripts.
Ravenports are compiled into a single “buildsheet”. Mistakes by
developers are caught during the compilation process, so syntax and
formatting are always correct. Unlike other frameworks, there’s
exactly one way to build Ravenports, meaning that if a new port or
modification builds successfully for a contributor, it will build
identically for an evaluator. Submission checks are capable of being
automated and performed against multiple platforms before a human ever
sees them. This leds to much better submissions and eliminates
unnecessary multiple review cycles.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-sitemap"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Inherent support of subpackages</h4>
<p>Other frameworks require separate ports if they want to split
documentation, examples, libraries, or anything other components into
separate packages to sanely satisfy dependency requirements. This
requires redundant rebuilding and risks getting related ports out of
sync. Ravenports allows many subpackages to be generated simultaneously
by a single port and this capability is heavily used. This allows for
fine-grain dependency specification (e.g. just pull a fortran runtime
library instead of the entire GCC compiler collection.)</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-tags"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Multiple package formats possible</h4>
<p>Currently only one package format is supported, which is the first
version defined by pkg(8), the FreeBSD package manager. This package
manager has been forked as ravensw(8) with new features as well as
enhanced portability. It has been throughly tested on all platforms
supported by Ravenports. Given interest, other package managers could
be supported such as the Image Packaging System (IPS), Arch Linux’s
pacman, Debian's DPKG family, etc.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-bank"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Enterprise friendly</h4>
<p>Ravenports was designed from the beginning to handle “custom” ports.
These allow, among other things, to freeze software at a specific version.
Companies are not forced to use the versions in quarterly sets or the
bleeding-edge tree, nor is support tied to the End-of-Life (EOL) of any
operating system release. Ports version tailoring can be provided as a
service to the company which has the added benefit of receiving security
updates on a weekly basis.</p>
<p>Using other frameworks can lead to frustration when help is urgently
needed but all the developers contribute on a volunteer basis. Corporate
users of Ravenports have the option of obtaining professional service when
required.</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-tree"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Entire tree integrity</h4>
<p>Other frameworks receive ports updates many times a day, sometimes
numbering in the hundreds. Coupled with a much lower quality (a result
of a wide range of volunteer developer skills coupled with little or no
quality assurance checks and impact assessments), ports trees break
frequently and often without addressing downstream breaking. Ravenports
stages the changes for several days. A complete build of the ports tree
is done to ensure tree integrity. The ports tree is published when
ready after any fallout issues are addressed to avoid surprises. This also
prevents temptation by users to update and rebuild daily, which would
result in constant and frustrating build churn. Finally, a roughly weekly
publishing schedule allows the ports tree and provided binary packages to
remain in sync, making it possible to safely mix ports and packages.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-tachometer"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Build performance</h4>
<p>This advantage does not benefit system adminstrators that exclusively
use prebuilt binary packages, but it is greatly appreciated by those that
build their own packages. Ravenports can scan and process the ports tree
hundreds to thousands of times faster than similar frameworks. Unlike the
others, Ravenports has an administration/build utility that’s fully
integrated and not a bolt-on tool. The utility, ravenadm, is written in
Ada and capable of high concurrency to take full advantage of powerful
build machines. Full tree scans which may take minutes (up to an hour on
pkgsrc) are accomplished in less than 1 second by ravenadm. Every aspect
of the framework is geared towards build quality and performance,
resulting in significantly shorter build times over comparable frameworks.</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-bars"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Concurrently installed versions</h4>
<p>Several popular projects maintain several branch releases. For
example, the Perl project has 3 concurrent versions. Python, Ruby,
most database servers and other projects do as well. Ravenports
always supports two versions of Perl and provides packages for both
which can be installed concurrently. The same case exists for Python
for the last two 3.x releases.</p>
<p>The PHP branches have unique installations so even multiple versions
of PHP can be installed together. Default database server versions can be
specified per repository, but currently only a single version can be
installed at a time.</p
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- About Section -->
<!-- Platforms --->
<section class="pricing" id="platforms">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Supported <span>Platforms</span></h3>
</div>
</div>
</div>
</div>
<div class="container single-blog">
<p class="text">
Ravenports has been designed to support any POSIX-compliant operating system
outside of Microsoft Windows. While it self-identifies as “universal”, Ravenports
must be bootstrapped to the point of self-hosting on each supported architecture
of each supported operating system. For the core developers, the main architectures
targeted are the <strong>x86_64</strong> and <strong>ARM64</strong>. New architecture
support from serious contributors capable of performing the initial bootstrap and
periodic quality-assurance builds of the entire Ravenports tree will be accepted
into the project.
</p>
</div>
<div class="container">
<div class="row">
<div class="col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="panel price panel-green">
<div class="panel-heading arrow_box text-center">
<h3>Current</h3>
</div>
<div class="panel-body text-center">
<p class="lead">Currently supported platforms</p>
</div>
<ul class="list-group list-group-flush text-center">
<li class="list-group-item"><i class="icon-ok text-success"></i> DragonFly 6.0 and later</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> FreeBSD/amd64 Release 12 and later</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> Linux/x86-64 (glibc 2.6.32-based)</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> macOS/Darwin x86_64 (<strong>on hold</strong>)</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> NetBSD/amd64</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> Solaris 10+ / illumos</li>
</ul>
<div class="panel-footer">
</div>
</div>
</div>
<div class="col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="panel price panel-green">
<div class="panel-heading arrow_box text-center">
<h3>Short Term</h3>
</div>
<div class="panel-body text-center">
<p class="lead">Platform support planned</p>
</div>
<ul class="list-group list-group-flush text-center">
<li class="list-group-item"><i class="icon-ok text-success"></i> FreeBSD/ARM64</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> Linux/ARM64</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> MidnightBSD/amd64</li>
</ul>
<div class="panel-footer">
</div>
</div>
</div>
<div class="col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="panel price panel-green">
<div class="panel-heading arrow_box text-center">
<h3>Long Term</h3>
</div>
<div class="panel-body text-center">
<p class="lead" title="Future support influenced by demand and contribution" style="cursor: pointer">Support increasingly unlikely</p>
</div>
<ul class="list-group list-group-flush text-center">
<li class="list-group-item"><i class="icon-ok text-success"></i> OpenBSD/amd64</li>
<li class="list-group-item"><i class="icon-ok text-success"></i> i386 (Linux and *BSD)</li>
</ul>
<div class="panel-footer">
</div>
</div>
</div>
</div>
</div>
<div class="container single-blog">
<p class="text">
A major requirement on platforms that are candidates for Ravenports
support is that a recent version of GCC must be available on the platform,
and must include fully functional C++, Fortran and Ada front-ends. For
exotic platform/architecture combinations, this may require cross-compilation
bootstrapping along with new support patches to bring Ada tasking capability
to the candidate platform.
</p>
</div>
</section>
<!-- Platforms --->
<!-- QuickStart -->
<section id="quickstart" class="site-padding">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Quick <span>Start</span></h3>
</div>
</div>
</div>
</div>
<div class="container single-blog">
<p>The section will be re-worked. The main User Guide has not been written.
The quickstart guides linked below tell how to install the Ravenports Administration
tool (ravenadm) with a host-specific system root and toolchain.
</p>
<p>There are complete repositories for each of the supported platforms, so anyone
familiar with pkg(8) on FreeBSD or DragonFly BSD will understand how to install the
prebuilt binaries immediately. Linux users may require finding FreeBSD-based tutorials
to grasp it better. This should be addressed in the upcoming user guides (TBW).</p>
<p>The ravenadm tool does have a complete set of man pages though. <strong>ravenadm help</strong>
will show those pages. Those familiar with the (d)synth port building tool on DragonFly
BSD or FreeBSD will quickly adapt to ravenadm, as it has the same look and feel, and also
has the web-based dynamic build report.</p>
</div>
<div class="news">
<div class="container">
<table>
<tbody>
<tr>
<td>DragonFly</td>
<td><a href="https://github.com/ravenports/Ravenports/wiki/quickstart-df">DragonFly BSD users Quick Start guide</a></td>
</tr>
<tr>
<td>FreeBSD</td>
<td><a href="https://github.com/ravenports/Ravenports/wiki/quickstart-freebsd">FreeBSD users Quick Start guide</a></td>
</tr>
<tr>
<td>Linux</td>
<td><a href="https://github.com/ravenports/Ravenports/wiki/quickstart-linux">Linux users Quick Start guide</a></td>
</tr>
<tr>
<td>NetBSD</td>
<td><a href="https://github.com/ravenports/Ravenports/wiki/quickstart-netbsd">NetBSD users Quick Start guide</a></td>
</tr>
<tr>
<td>Solaris</td>
<td><a href="https://github.com/ravenports/Ravenports/wiki/quickstart-sunos">Solaris/illumos users Quick Start guide</a></td>
</tr>
<tr>
<td>macOS</td>
<td>(Note: Platform currently on hold!) <a href="https://github.com/ravenports/Ravenports/wiki/quickstart-macos">macOS/Darwin users Quick Start guide</a></td>
</tr>
</tbody>
</table>
</div>
</div>
</section>
<!-- Schedules -->
<section id="schedule" class="site-padding">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Update <span>Schedule</span></h3>
</div>
</div>
</div>
</div>
<div class="container single-blog">
<p class="text">
The source tree for Ravenports is under constant update. However, the
Ravenports tree is only generated on roughly a weekly basis. Minor updates to
heavily used ports can cause the majority of the tree to require a rebuild,
so the policy is to provide all the updates in one step.
</p>
</div>
<div class="container">
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa icon-perl"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Perl ports</h4>
<p>With many thousand perl modules with CPAN, updates are seen many times per day.
Perl alone causes serious build churn based on these daily updates, and that’s
without any kind of integrity checking. Therefore the policy is to update perl
modules a couple of times per week. Before a release is tagged, a full build
check is performed internally to ensure the perl ecosystem remains functional.</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa icon-python "></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Python ports</h4>
<p>Python modules are similar to perl, but are more volatile. Typically python
modules are updated the same day as perl, and they are also integrity build-tested
before a release is tagged.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="row">
<div class="col-sm-6">
<div class="single-feature wow fadeInLeft">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-shield"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Security and vulnerability updates</h4>
<p>For non-commercial users, security updates appear as regular updates with every
release. These updates may appear as version updates. Commercial service users that
have specified and locked down software versions (older than the current Ravenports
tree) will receive security as port revisions accompanied by patches each Tuesday.
If patches aren’t feasible, the client will be informed as soon as possible to
determine how best to address newly-known security issue.)</p>
</div>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="single-feature wow fadeInRight">
<div class="row">
<div class="col-md-2">
<div class="feature-icon">
<i class="fa fa-download"></i>
</div>
</div>
<div class="col-md-10">
<div class="feature-text">
<h4>Binary package updates</h4>
<p>As soon as the Ravenports tree is generated, incremental building of packages will commence on all supported repositories. Depending on the extent of the changes, new packages should be available within a few hours to a couple of days after the generation of the source tree. For commercial service clients, a notice will be sent when new packages are ready for download.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- Schedules -->
<!-- Contributing -->
<section id="contributing" class="site-padding">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Volunteer <span>Contributions</span></h3>
</div>
</div>
</div>
</div>
<div class="container">
<p>Every leg of the Ravenports Triad consists of Free and
Open-Source Software (FOSS), released under the permissive
Internet Systems Consortium (ISC) License. Contributions are
welcome and may appear in many forms, such as:</p>
<div class="contrib">
<ul>
<li>bug reports</li>
<li>patch submissions</li>
<li>port adoption and maintenance</li>
<li>Binary package and repository generation</li>
<li>Security vulnerability reports</li>
<li>Submission of new ports</li>
</ul>
</div>
<div class="contrib-entry">
<h4>Bug and Security vulnerability reports</h4>
<p>In the future, we may host a dedicated issue tracking system.
For the time being, the Github issue tracking system is available
for users to report bugs and any security issues that may not have
been known or addressed yet.</p>
<p>Report here:
<a href="https://github.com/ravenports/ravensource/issues">https://github.com/ravenports/ravensource/issues</a></p>
</div>
<div class="contrib-entry">
<h4>Submission of patches and new ports</h4>
<p>In the future, submission of patches and new ports will be done
through a dedicated interface that will put the submission in a build
queue and test build the affected ports on all supported platforms
automatically. If the build tests pass automated tested, the submissions
will be forward for human inspection and inclusion. However, we aren’t there yet.</p>
<p>All patches must be build tested locally. If they pass the submitter’s
own testing, the best approach is to submit the contribution as a github
pull request here:
<a href="https://github.com/ravenports/customsource/pulls">https://github.com/ravenports/customsource/pulls</a></p>
<p>The process is the same when submitted an entirely new port, with one
additional requirement. The person that creates and submits the port
agrees to be listed as the port’s maintainer for at least 6 months. It
is expected that submitter fully tests the new port on at least one platform.</p>
<p>The pull request description for a new port should provide the follow information:</p>
<div class="contrib">
<ul>
<li>Synopsis of what functionality the new port provides (what the software does)</li>
<li>Impact of not approving the port for inclusion</li>
<li>Optionally: what type of user is likely to benefit from its inclusion</li>
<li>Which platform(s) the port was tested on</li>
</ul>
</div>
</div>
<div class="contrib-entry">
<h4>Port adoption</h4>
<p>Each port may have one or more maintainers. Most ports have no listed
maintainer or are generated by a script. There are benefits to having a
specific person or team of people responsible for maintenance and update of
a port. Ideally the maintainer should be a regular user of the port’s software.
This helps porting errors to be detected quickly and also allows for quick
confirmation of reported bugs. A real user is more motivated to fix bugs and
keep up with the latest software upgrades.</p>
<p>Those volunteering to be the primary maintainer of a port are expected to
be familiar with the
<a href="https://github.com/ravenports/Ravenports/wiki/Ravenporters_Guide">Ravenporter's Guide</a>
and have the technical skills necessary for basic port maintenance and
troubleshooting. They are also expected to handle bug reports to their
natural conclusion. If multiple maintainers are listed on a port, they are
expected to communicate internally (each speak for the others on bug
trackers, etc.).</p>
<p>Requests to adopt ports can be made either through the Github issue
tracker or submitted as changes via a github pull request. The latter
method is preferred.</p>
</div>
<div class="contrib-entry">
<h4>Binary package and repository generation</h4>
<p>This contribution forms when somebody wishes to extend Ravenports
support to lesser-used platforms or architectures. The new platform support
requires the contributor to have the necessary hardware to accomplish the
system root and toolchain bootstrapping. Additionally the contributor is
expected to build a complete set of binary packages and upload them at regular
intervals. That will likely require per-platform adjustments to existing and
incoming ports, so this is not a trivial contribution. Serious contributions are
more than welcome, but there will be some vetting to ascertain the skill level
and the commitment level of any person or team offering to extend Ravenports
for non-commercial support use.</p>
</div>
</div>
</section>
<!-- Contributing -->
<!-- FAQ DISABLED - - >
<section id="news">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Frequently Asked <span>Questions</span></h3>
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-md-6">
<div class="panel-group" id="accordion">
<div class="faqHeader"><h4>01. FAQ Header Title Goes Here</h4></div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseOne">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseOne" class="panel-collapse collapse in">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseTen">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseTen" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseEleven">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseEleven" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="faqHeader"><h4>03. FAQ Header Title Goes Here</h4></div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseFour">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseFour" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseSeven">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseSeven" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
</div>
</div>
<div class="col-md-6">
<div class="panel-group" id="accordion">
<div class="faqHeader"><h4>04. FAQ Header Title Goes Here</h4></div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseNew">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseNew" class="panel-collapse collapse in">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseNewOne">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseNewOne" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
<div class="faqHeader"><h4>06. FAQ Header Title Goes Here</h4></div>
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a class="accordion-toggle collapsed" data-toggle="collapse" data-parent="#accordion" href="#collapseNewFour">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
</h4>
</div>
<div id="collapseNewFour" class="panel-collapse collapse">
<div class="panel-body">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!--FAQ-->
<!-- News -->
<section id="news" class="site-padding">
<div class="container">
<div class="row">
<div class="col-sm-12">
<div class="title">
<h3>Latest <span>News</span></h3>
</div>
</div>
</div>
</div>
<div class="news">
<div class="container">
<table>
<tbody>
<tr>
<td>2023-08-25</td>
<td>Major toolchain upgrade: All packages are now built with <em>GCC 13.2.0</em>
and <em>binutils 2.41</em> instead of 11.2.0 and 2.35.1. Also the sysroots port
has been split to one per operating system. <em>DragonFly BSD</em> and <em>FreeBSD</em>
have had standard variants for versions <em>6.4</em> and <em>13.2</em> added
in addition to the previous 6.2 and 12.2 respectively (rather then replacing them).
Linux/glibc now has a new standard variant based on Debian 12 in addition to
Ubuntu 16.04.</td>
</tr>
<tr>
<td>2023-04-17</td>
<td><em>MidnightBSD</em> is now supported. Platform bring-up has been completed
and an initial package set uploaded. A new USES module (mbsdfix) was added to
the framework to automatically handle software with too old configure scripts.</td>
</tr>
<tr>
<td>2023-01-24</td>
<td>The packaging scheme is being reorganized: Development files will be split
out into subpackages, same for manpages. It is expected to complete this for all
the ports with <em>single</em> variants in two weeks or so. The rest will be
converted over time during regular port version upgrades and maintenance. Also
the first bunch of KDE ports have been committed. Work on that has stopped, though
(missing wayland support on most platforms makes it impractical).</td>
</tr>
<tr>
<td>2022-10-15</td>
<td>A new <em>Ravenports</em> organization has been created on GitHub
and all relevant repositories were transferred over.</td>
</tr>
<tr>
<td>2022-09-06</td>
<td>Ravenports switched away from GL libreries provided by <em>mesa</em> to those
from <em>libglvnd</em>. While reworking many ports as part of the graphics stack
migration, introspection has been made optional for many GTK-based ports.</td>
</tr>
<tr>
<td>2021-10-20</td>
<td><em>NetBSD</em> support is now available. Various problems had to be solved to
bring the modern Ravenports toolchain over and to work with some specifics
of that platform. Work on fixing several ports is ongoing but a considerable
number of packages are already available.</td>
</tr>
<tr>
<td>2021-08-25</td>
<td>Major toolchain upgrade: All packages are now built with <em>GCC 11.2.0</em>
and <em>binutils 2.35.1</em> instead of 9.3.0 and 2.34. The exception here is
Solaris since GCC 10+ do no longer support Solaris 10. The very old system
libraries of 10u8 have become a more and more of a problem for various ports. The
most likely path forward will be to drop Solaris support and pick a modern
illumos distribution instead.</td>
</tr>
<tr>
<td>2020-12-26</td>
<td><em>FreeBSD base system</em> has been upgraded from 11.1 to 12.2. This means
that all packages built from now on require <em>12.2-RELEASE</em> or later.</td>
</tr>
<tr>
<td>2020-06-07</td>
<td>Everything necessary to work with <em>TeX</em> has now been added to
Ravenports, finishing a major porting effort. Packages for the full <em>TeXlive
2020</em> distribution are available with subpackages for the engines and other
components to pick from. The latest versions of the TeX IDE <em>texstudio</em> and
the WYSIWYM TeX document processor <em>LyX</em> are available as well.</td>
</tr>
<tr>
<td>2020-05-11</td>
<td>Ravenports now supports <em>CPE</em> information. It has already been added to
most of the existing ports.</td>
</tr>
<tr>
<td>2020-04-15</td>
<td>A new <em>nls</em> subpackage has been introduced and ports that previously
supported internationalization via variants have been converted. It is
expected that all new ports will offer localization support (if applicable)
and the existing ones that could support it will do so in time, too. Also a port
for the <em>R language</em> has been added as well as a facility to auto-create
R ports from CRAN.</td>
</tr>
<tr>
<td>2019-11-22</td>
<td>Major toolchain upgrade: All packages are now built with <em>GCC 9.2.0</em>
and <em>binutils 2.33.1</em> instead of 8.3.0 and 2.32.</td>
</tr>
<tr>
<td>2019-07-19</td>
<td>Ravenport's fork of FreeBSD's package manager has been renamed from
<em>pkg</em> to <em>ravensw</em> and various additional portability fixes were
added. Unfortunately it's still flaky on Linux.</td>
</tr>
<tr>
<td>2019-02-19</td>
<td>Ravenports supports installing more than one <em>TLS library</em> (libressl,
openssl, libressl-devel, openssl-devel) on the same system at the same time. This
makes it possible to install software with specific requirements that were mutually
exclusive before. Support for the <em>MacOS</em> platform is on hold for now.</td>
</tr>
<tr>
<td>2018-12-22</td>
<td><em>Rust</em> is now available on all platforms except Solaris/illumos and MacOS.