Re: Misleading directory names

[Antonio Huete Jimenez <ahuete.devel@xxxxxxxxx>]

Hi Prezemylaw,

I know no OS which is finished. There's always things to do ;)

Besides that I think the amd64 symlink could be removed as there's no
2.6/2.7 release with arch. name, but it isn't either a big deal.

Cheers,
Antonio Huete

2010/9/28 Przemysław Pawełczyk <pp_o2@o2.pl>:
> On Tue, 28 Sep 2010 03:30:28 -0600
> "Samuel J. Greear" <sjg@evilcode.net> wrote:
>
>> 2010/9/28 Przemysław Pawełczyk <pp_o2@o2.pl>:
>> > Hi,
>> >
>> > Listing from http://avalon.dragonflybsd.org/packages/
>> >
>> > Name         Last modified      Size  Description
>> > Parent Directory                  -
>> > README       18-May-2010 02:45  1.3K
>> > amd64/       24-Aug-2010 23:56    -
>> > i386/        27-Sep-2010 20:59    -
>> > x86_64/      24-Aug-2010 23:56    -
>> >
>> > Why there are two __identical__ directories under __two__ different
>> > names which stand for the same contents?
>> >
>> > Excerpt from README:
>> >
>> > What's here
>> > ------------
>> >
>> > The i386 directory contains packages built on 32-bit DragonFly
>> > systems. The amd64/x86_64 directores contains packages built on
>> > 64-bit DragonFly systems.
>> >
>> > (amd64 and x86_64 are the same thing here)
>> >                  ^^^^^^^^^^^^^^^^^^^^^^^
>> >
>> > Why the mess?
>> >
>> > Regards
>> >
>> > --
>> > Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick]
>> > http://pp.blast.pl, pp_o2@o2.pl
>> >
>>
>> Our x86_64 branch used to be called amd64, it's just legacy.
>>
>> Sam
>
> Hi,
>
> 1. Having DFBSD so young and calling former releases "a legacy" is kinda
> hoity-toity. ;-) AFAIK the DFBSD is not __finished__ yet so former
> versions were at best development releases.
>
> 2. Would you put the information about legacy into every nook and
> cranny of DFBSD documentation? Nope. What's the purpose then to litter
> DFBSD and mirror servers with the Doublespeak? ;-) Let bygones be
> bygones. ;-)
>
> Regards
>
> --
> Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick]
> http://pp.blast.pl, pp_o2@o2.pl
>