Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2012-09

About Putting everything in one repo

12 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Zaher Dirkey

Hi, FPC and Lazaurs team

I noticed there is new component (PascalScript) ported to lazarus/components/ and in the past AggPas also ported, The idea, why you put many components not used for most users, same ask in FPC

My example to understand me

I use SQLite, we found a bug and this bug fixed by FPC team, now we must wait long time to have new release with this simple bug fixed. But if the SQLite unit in another repository, this Extended repo can published the releases more faster than FPC releases, If FPC release come one every year this repo collected and released 4 time in this year.

Same idea for Lazarus, i know Lazarus has Lazarus-ccr, for that i asked why you extending the Components directory in the official Lazarus repository.

Sorry for my poor English.

Best Regards
Zaher Dirkey

Florian Klämpfl
to Zaher Dirkey
Zaher Dirkey wrote 13 lines
Hi, FPC and Lazaurs team I noticed there is new component (PascalScript) ported to lazarus/components/ and in the past AggPas also ported, The idea, why you put many components not used for most users, same ask in FPC My example to understand me I use SQLite, we found a bug and this bug fixed by FPC team, now we must wait long time to have new release with this simple bug fixed. But if the SQLite unit in another repository, this Extended repo can published the releases more faster than FPC releases,

If somebody is interested to do so, he can do this. What does prevents someone technically (!) from releasing SQLit unit update installers from the currently used repository?

Martin
to Zaher Dirkey: Hi, FPC and Lazaurs team I noticed there is new component (PascalScript) ported to…
Zaher Dirkey wrote 5 lines
Hi, FPC and Lazaurs team I noticed there is new component (PascalScript) ported to lazarus/components/ and in the past AggPas also ported,

...

Show quoted text 5 lines
I use SQLite, we found a bug and this bug fixed by FPC team, now we must wait long time to have new release with this simple bug fixed. But if the SQLite unit in another repository, this Extended repo can published the releases more faster than FPC releases, If FPC release come one every year this repo collected and released 4 time in this year.

The reason Pascalsript went into the main SVN is, that (if all goes well) then it will be used by the IDE itself. So the IDE will need it to be build.

Zaher Dirkey
to Florian Klämpfl: If somebody is interested to do so, he can do this. What does prevents someone…
Florian Klämpfl wrote
If somebody is interested to do so, he can do this. What does prevents someone technically (!) from releasing SQLit unit update installers from the currently used repository?

Partial agree, but
In another repo, you can have separated milestones, bugs must finished before release the new version, it is like when release Lazarus based on the same versions of FPC.

Not only Sqlite, there is many packages like it, sqlite here for example.

snapshots not resolve the problem because it have included the core of FPC, and it is not stable.

Best Regards
Zaher Dirkey

Reinier Olislagers
to Zaher Dirkey
Zaher Dirkey wrote 18 lines
On Sun, Sep 2, 2012 at 1:20 PM, Florian Klämpfl < > wrote: If somebody is interested to do so, he can do this. What does prevents someone technically (!) from releasing SQLit unit update installers from the currently used repository? Partial agree, but In another repo, you can have separated milestones, bugs must finished before release the new version, it is like when release Lazarus based on the same versions of FPC. Not only Sqlite, there is many packages like it, sqlite here for example. snapshots not resolve the problem because it have included the core of FPC, and it is not stable.

Why don't you use FPC fixes (e.g. FPC 2.6.1) then, and help backport stable fixes from trunk to fixes?

Reinier Olislagers
to Zaher Dirkey
Zaher Dirkey wrote 11 lines
On Sun, Sep 2, 2012 at 2:25 PM, Reinier Olislagers < > wrote: Why don't you use FPC fixes (e.g. FPC 2.6.1) then, and help backport stable fixes from trunk to fixes? Is that in the download page?

It's a branch in the svn repository. And Lazarus builds based on fixes 2.6 appear on the snapshots page. For Linux/OSX, you'll probably find those on the snapshots page.
For fpc only: see also
http://www.freepascal.org/develop.var

Anyway, I'd rather use svn - of course, in my case fpcup ;) because I don't want to download the entire distribution all the time, only the changes.

And is it have the last fixed for this kind of non core packages?

It has the last fixes that were considered stable and were backported for all FPC packages.

Zaher Dirkey
to Reinier Olislagers

On Sun, Sep 2, 2012 at 2:55 PM, Reinier Olislagers <

Show quoted text 13 lines
wrote: It's a branch in the svn repository. And Lazarus builds based on fixes 2.6 appear on the snapshots page. For Linux/OSX, you'll probably find those on the snapshots page. For fpc only: see also http://www.freepascal.org/develop.var Anyway, I'd rather use svn - of course, in my case fpcup ;) because I don't want to download the entire distribution all the time, only the changes.

It is for expert user not for normal user.

> And is it have the last fixed for this kind of non core packages? It has the last fixes that were considered stable and were backported for all FPC packages.

So, i prefer to make fixes snapshots in the main downloads page but with minor version number like this 2.6.0.1, because: how can i publish my project and mentioned what snapshot must used to work or compiled?.

Best Regards
Zaher Dirkey

Reinier Olislagers
to Zaher Dirkey
Zaher Dirkey wrote 16 lines
On Sun, Sep 2, 2012 at 2:55 PM, Reinier Olislagers < > wrote: It's a branch in the svn repository. And Lazarus builds based on fixes 2.6 appear on the snapshots page. For Linux/OSX, you'll probably find those on the snapshots page. For fpc only: see also http://www.freepascal.org/develop.var Anyway, I'd rather use svn - of course, in my case fpcup ;) because I don't want to download the entire distribution all the time, only the changes. It is for expert user not for normal user.

Nothing difficult in running fpcup ;)
Regardlessly, have a look at the pages I linked to for the nightly download.

Show quoted text 8 lines
> And is it have the last fixed for this kind of non core packages? It has the last fixes that were considered stable and were backported for all FPC packages. So, i prefer to make fixes snapshots in the main downloads page but with minor version number like this 2.6.0.1, because: how can i publish my project and mentioned what snapshot must used to work or compiled?.

If the fixes branch breaks it needs to be... fixed. Because only fixes, no new functionality, are backported to FPC fixes after having been tested for a while in FPC trunk, that shouldn't happen very much.

Apart from that I don't really understand. Are you saying you want to maintain your own FPC distribution that contains fixes so people can use it to compile your software?

Sounds like a lot of work.

Zaher Dirkey
to Reinier Olislagers

On Sun, Sep 2, 2012 at 3:30 PM, Reinier Olislagers <

Show quoted text 6 lines
wrote: Apart from that I don't really understand. Are you saying you want to maintain your own FPC distribution that contains fixes so people can use it to compile your software?

No :)

I need more faster release versions, no need to include release a core files, only packages with minor version number, most product i used it have this release like PHP, SQLITE, FirebirdSQL.

not using snapshots or SVN.

Best Regards
Zaher Dirkey

Sven Barth
to Zaher Dirkey: Hi, FPC and Lazaurs team I noticed there is new component (PascalScript) ported to…
Zaher Dirkey wrote 14 lines
Hi, FPC and Lazaurs team I noticed there is new component (PascalScript) ported to lazarus/components/ and in the past AggPas also ported, The idea, why you put many components not used for most users, same ask in FPC My example to understand me I use SQLite, we found a bug and this bug fixed by FPC team, now we must wait long time to have new release with this simple bug fixed. But if the SQLite unit in another repository, this Extended repo can published the releases more faster than FPC releases, If FPC release come one every year this repo collected and released 4 time in this year.

There is the idea to have some/most/all units under packages being distributed by a FPC package manager (which already exists more or less: fppkg) which can update the installed packages. The switch from fpcmake to fpmake is a first step in that direction, but I don't know how high the motivation for a package manager is...

Note: In concept it would be similar to package managers for other programming languages like Python, Ruby or Lua.

Regards,
Sven