Hello,

Thanks for the answers!


On Sat, 25 Jun 2022 at 22:32, Jerome Shidel <jer...@shidel.net> wrote:

> For example, if KEYB on the GitLab archive has a commit pushed with the
> comment “Fixed double keypress bug”. That comment would appear in the
> CHANGES.LOG as something like “2022-06-29 04:52:11 keyb (Aitor Santamaría):
> Fixed double keypress bug”
>

Ok, commit logs are a good source too, but this advices to write good
(user-readable) commit logs.


> Finally, what path on ibiblio do you want to use to provide package
>> updates? This has nothing to do with creating the interim build. As you
>> recall, the current RBE uses the GitLab FreeDOS Archive (
>> https://gitlab.com/FreeDOS) to create the packages on the release. It
>> can also automatically pull specific branches of those packages based on
>> the release, interim, development or other type of build it is creating.
>> The package update url only applies to where the release / interim build
>> will check for package updates.
>>
>> I think it makes sense to keep it along side the other OS update
>> repositories. There are already repositories for each Release
>>
>> 1.1 -
>> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.1/
>> 1.2 -
>> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/
>> 1.3 -
>> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/
>>
> I don't know if I am getting this well: this means that in the 1.2 folder
> you find the packages updated over 1.2?
> This means that if at this moment there appears a new updated package that
> hasn't been updated earlier, it should go into ALL of the 1.1, 1.2 and 1.3
> folders?
>
>
> Basically, yes. There is a separate software update repository for
> maintained for each of OS release.
>

It would be for each major, or for every unstable too? (in the latter, it'd
require a lot of space, right?)

Aitor
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to