Re: GoboLinux 015 beta3.

On 21 April 2014 12:50, Lucas C. Villa Real <[email protected]> wrote:
> On Mon, Apr 21, 2014 at 12:13 PM, K Lowe <[email protected]> wrote:
>>
>> Hi Lucas,
>>
>> Delighted to inform you that I was able to install (full) GoboLinux
>> successfully.

Many thanks for the feedback!!

>> However:
>>
>>  - Perhaps for those not familiar with Enlightenment window manager there
>> should be an opportunity to install an alternative desktop environment,
>> e.g., XFCE or LXDE, either as a separate ISO or as an option in the
>> GoboLinux Installer.
>
>
> We have thought about that, but we wanted to limit the number of desktop
> environments to keep the distribution simple to maintain. As you may have
> noticed, we had KDE4 in beta2 and it has been removed from beta3 to keep
> things simple. We may offer extra window managers as binary packages on
> gobolinux.org once the final ISO is announced.

I'm considering adding something minimal, such as OpenBox or
WindowMaker, as an alternative, but no promises.

If anyone really wants that, help with packaging is most welcome:

* micro 3-step how-to add packages and contribute recipes:
1) MakeRecipe mypackage 1.0 http://example.com/mypackage-1.0.tar.gz
2) Compile mypackage
3) ContributeRecipe mypackage 1.0

* OpenBox (or equivalent) will need configuration files to be included
in the Live ISO to make it usable. Tips and suggestions on how to
better set it up are welcome!

>>  - No FlashPlayer plugin for Firefox was installed.
>
> There is a distribution license that one needs to request from Adobe to ship
> the FlashPlayer plugin:
> http://www.adobe.com/products/flashplayer/distribution3.html and
> http://www.adobe.com/uk/products/players/flash-player-distribution.html
>
> I do not feel very comfortable with that.

If anyone would like to write a InstallFlash shell script which
downloads Flash from Adobe, shows the end-user agreement and unpacks
and places it in ~/.mozilla/plugins, I think we could add the script
to the ISO.

>> ]Compile Freshen (Okay)
>> ]Freshen
>> ...
>> Freshen has encountered an internal error.

`Freshen -r` should work fine.

We probably won't be maintaining binary packages in the near future,
so that's the only mode of operation that matters right now, anyway!

-- Hisham