| 1 |
I'm busy adding a pair of applications to net-misc. |
| 2 |
Both of them are named the same thing 'aggregate' by their authors. |
| 3 |
They were written independantly by their authors with no knowledge of |
| 4 |
the other, and both started around the same time. |
| 5 |
|
| 6 |
One is listed on freshmeat as 'aggregate flim' (referred to as #2 from |
| 7 |
here on) and the other as 'aggregate' (refered to as #1 from here on). |
| 8 |
|
| 9 |
Both of them perform basically the same function, optimizing CIDR style |
| 10 |
addresses, but have slightly different different feature sets. |
| 11 |
|
| 12 |
#1 is capable of handling Cisco IOS style masks, and can clean up |
| 13 |
invalid CIDR inputs like 12.13.14.16/24 (cleans to 12.13.14.0/24). |
| 14 |
|
| 15 |
#2 can handle input and output in netmask and range styles in addition |
| 16 |
to CIDR style as well as suppress listings outside a given prefix range. |
| 17 |
|
| 18 |
I presently use both of them as |
| 19 |
(source) | #1 | #2 | (destination) |
| 20 |
|
| 21 |
Source file for #1 is 'aggregate-1.6.tar.gz' |
| 22 |
Source file for #2 is 'aggregate-1.0.2.tar.gz' |
| 23 |
|
| 24 |
Short of re-writing the code to merge the two featuresets, what's the |
| 25 |
best course of action for handling this properly in the tree? |
| 26 |
|
| 27 |
For the moment, #1 installs as 'aggregate' and #2 installs as |
| 28 |
'aggregate-flim' and they have those names in the tree. |
| 29 |
|
| 30 |
I suppose the problem will get worse if the versions ever sync up |
| 31 |
between two identically named packages. |
| 32 |
|
| 33 |
-- |
| 34 |
Robin Hugh Johnson |
| 35 |
E-Mail : robbat2@××××××××××××××.net |
| 36 |
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 |
| 37 |
ICQ# : 30269588 or 41961639 |
| 38 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives