|Apollo Team Commitment to AROS 68k Development||page 1 2 3 4 5 6 7 8 |
25 Sep 2019 22:10
|Nice, if that's the case as the v4 and 500v2 use their own ide interface that issue must be resolved. Though I'll stick with coffin for now till I get it up and running fully.|
Might see about setting up another cf card with Aros on it.
25 Sep 2019 23:01
|wawa t wrote:|
there is installer and we have an open source installer replacement as well. (which is being built at amigaports along with aros68k.)
My wrong. I ment package manager.
At least some kind of system update tool should be shipped with the AROS version that comes with the Vampire hardware. It will for sure be a lot of updates in the beginning. The installer can be used as a update tool but I rather see a package manager that fetch from the net and give info about updates.
26 Sep 2019 00:34
|A server for Grunch would probably do the job. EXTERNAL LINK |
26 Sep 2019 01:06
|Samuel Crow wrote:|
A server for Grunch would probably do the job. EXTERNAL LINK
That does not work :(
Every time I try to update the database it returns with 0 byte and failure. Most of the items listed in Grunch is old and cannot be downloaded.
26 Sep 2019 04:43
|Im just wondering whether we can hold off from bogging the team down with too many wishlists at this point in time and just allow them to improve AROS' compatibility and efficiency. Once this is done then perhaps features can be added. Im worried if we demand too much too early we may scare the devs off. This has happened in the past and I don't want it to happen again. Just a suggestion. :) |
Posts 1896/ 1
26 Sep 2019 06:22
|Agreed. There Is a lot of work now to properly adopt Aros and optimise and improve KS.|
I ll hold my dreams for 2020
26 Sep 2019 07:04
|yeah. packaging systems in a community where just few people bother to lift a finger to do anything. go figure.|
26 Sep 2019 09:39
|sean sk wrote:|
Im just wondering whether we can hold off from bogging the team down with too many wishlists at this point in time and just allow them to improve AROS' compatibility and efficiency. [..] Im worried if we demand too much too early we may scare the devs off. This has happened in the past and I don't want it to happen again.
I also think that it is important no to overload the team and future plans. I think the Apollo Team should (be able) to concentrate to core (technical) aspects of AROS and that the rest (for example a package manager) should come from the community. I'm actually waiting for "my" V4-SA (I ordered one via Relec) and can't wait (a) to get it :) and (b) start coding and contribute to AROS (I have been looking at the codebase and have to say that the task is daunting - and that it may take a lot of time for new developpers to understand how things work) - but I think that we should really try to bring this forward. I my opinion the situation of AROS now is comparable to Linux in the 90ies (and thus has potential to grow).
26 Sep 2019 11:31
|@Red Bug: Exactly... what a nice challenge... :)|
Also, people always complain about Amiga OS not being open source or not happening enough with it.
Now everybody can contribute..
26 Sep 2019 13:10
|I think you don't want to make things difficult for the end user.|
This is why the packet manager or similar is a good idea.
It will be much more pain in the end for the Vampire team if they don't do something about this.
Just wait to see the complaints from People that have done this and that to install updates and mess around with the system.
This will happen anyway, but then the Vampire team can say we don't give any garantee if you use other way to update the system than our solution.
In a Perfect world AROS would be well tested and developed by the Vampire team, but it is not like that.
26 Sep 2019 13:30
|Lets not forget that the team still has other Vampire tasks to work on. For example, my A1200 is waiting for a Vampire card and the Gold 3 release needs to be back-ported to the v2 cards.|
26 Sep 2019 14:40
|Nobody responds to the back port of Gold 3 Tim. I am starting to think that it is unlikely.|
26 Sep 2019 15:52
|David Wright wrote:|
Nobody responds to the back port of Gold 3 Tim. I am starting to think that it is unlikely.
They needed to actually finish it for the V4SA first. Then they will try to backpprt as much as they can fit into the V2 FPGA after that. I think it will happen, just will take a little time. Not like they could do it before they finished it for the v4...
26 Sep 2019 17:45
|I tought the Vampire team would have AROS boundled not only as rom, but also on a Storage Device.|
Posts 1896/ 1
26 Sep 2019 18:08
|Gold3 cores for v2 will happen after v4sa stable cores, maybe even after "v4 for all classics"|
As of wishes, such as x86 backports, smp, update repo or Linux kernel I do understand v4 and v2 Gold3 and now improved Basic Aros Are xurrent team priorities.
I just want user wishes to be on next year roadmap.
Amiga land teaches patience is virtue
26 Sep 2019 20:15
|All good plans include plans to reevaluate the plans and make necessary adjustments.|
At or shortly after Amiga34, IMHO, it would be a good time to reevaluate their plans, make an updated roadmap and communicate it to the community.
Gunnar von Boehn
(Apollo Team Member)
27 Sep 2019 07:15
|AIBB running on V4 on AROS|
Posts 1896/ 1
28 Sep 2019 21:55
|AROS Package Manager has an open bounty at P2P|
AROS Package Format and Management Tools
Provide a working environment for installing, updating and maintaining Packages on AROS platforms
Package File Format: Provide a suitable Package Format for installing and distributing AROS software. You will neeed to provide a means for storing all a packages necessary components in a single file preferably using a standard archive file format which must be suitable for use within AROS. You should provide means for packages to describe themselves, and for them to handle scripts necessary for the Package Manager and Installer to correctly utilise the packages as described below. You must idnetify and document all the components necessary to make packages work as intended. Packages must be provided using a namespace suitable for multiple architectures and versioning or date
Package Manager: Must be able to check installed Packages on an AROS system and allow users to upgrade from online sources seereferencenumber1 or localy stored packages. Package Installation will involve Package Manager retrieving the correct packages, extracting them as necessary, and passing the correct scripts to the AmigaOS / AROS Installer. Users must be able to Install, Uninstall and Validate Installations using the Package Manager. Dependencies for packages should be handled by the Package Manager but processed via the Installer
Package Repository: Implement and document a working repository for AROS software which can be utilised by the AROS Package Manager to upgrade/install components on an AROS platform. See note number1 Packages must be identifiable for a particular platform, installable via the package manager, and should be available via applicable software categories.
Package Installation: By providing a Front end to or by updating Installer itself, enable the Installer to handle the scripts used by the AROS Package Manager. It must be able to Check Dependencies, Install, Uninstall and Validate a Package installation via standard AmigaOS style Installer scripts.
Note Number 1: preferably using a distributed technology such as torrents
28 Sep 2019 22:52
|Can something like APT just not be ported? I mean I donít see a reason to reinvent the wheel here from scratch. Or does it have something to do with the way installer works?|
29 Sep 2019 05:32
|Mike Kopack wrote:|
Can something like APT just not be ported? I mean I donít see a reason to reinvent the wheel here from scratch. Or does it have something to do with the way installer works?
Apt doesn't even work on non-Debian versions of Linux, let alone foreign operating systems.