This is a new bug that tries to start splitting the fpc stuff into multiple packages since the fpc package is too big and nobody needs all that at once. I dont know if I choose the split version or the huge version as final yet so keep both open Reproducible: Always Steps to Reproduce: 1. 2. 3.
note that the big standalone ebuild is bug#79985
as precoditions this needs: a new category in /usr/portage/categories: dev-fpc a new eclass in /usr/portage/eclass/fpc.eclass
I plan fpc cvs version at first
Created attachment 49961 [details] fpc compiler ebuild, put into dev-lang/fpc the main fpc compiler ebuild, to be put into dev-lang/fpc does not install utils (= fpcmake etc which could very well be needed to compile an app... ) (perhaps change that later)
Created attachment 49963 [details] fpc compiler ebuild, put into dev-lang/fpc fpc compiler ebuild, put into dev-lang/fpc (without utils like fpcmake ...)
Created attachment 49968 [details] fpc icon: dev-lang/fpc/files
Created attachment 49981 [details] dev-fpc/paszlib ebuild dev-fpc/paszlib ebuild, one of the base packages needed
Created attachment 49982 [details] dev-fpc/netdb ebuild dev-fpc/netdb, one of the base packages
Created attachment 49983 [details] default fpc.cfg, for dev-lang/fpc ebuild into files subdir default fpc.cfg, for dev-lang/fpc ebuild into files subdir
Created attachment 49984 [details] default fpc.cfg, for dev-lang/fpc ebuild into files subdir default fpc.cfg, for dev-lang/fpc ebuild into files subdir. use $fpctarget since that is handled by fpc itself
Created attachment 49985 [details] fpc compiler ebuild, put into dev-lang/fpc using $fpctarget
Created attachment 49986 [details] fpc compiler ebuild, put into dev-lang/fpc using $fpctarget
Created attachment 49987 [details] fpc compiler ebuild, put into dev-lang/fpc fpc compiler ebuild, put into dev-lang/fpc
Created attachment 49991 [details] fpc eclass, for now fpc eclass, for now
todo, set 'DESCRIPTION' for most of the ebuilds
Created attachment 49992 [details] dev-fpc/paszlib ebuild update DESCRIPTION
Created attachment 49993 [details] dev-fpc/netdb ebuild dev-fpc/netdb ebuild, update DESCRIPTION
Created attachment 50000 [details] dev-fpc/libasync ebuild dev-fpc/libasync ebuild
Created attachment 50001 [details] dev-fpc/pthreads ebuild dev-fpc/pthreads ebuild
Created attachment 50002 [details] dev-fpc/pasjpeg ebuild pasjpeg ebuild
Created attachment 50003 [details] dev-fpc/ibase ebuild dev-fpc/ibase ebuild
Created attachment 50010 [details] fpc eclass, works fpc eclass, works, with BASE flag
Created attachment 50011 [details] dev-fpc/paszlib ebuild dev-fpc/paszlib ebuild
Created attachment 50012 [details] dev-fpc/netdb ebuild dev-fpc/netdb ebuild
Created attachment 50013 [details] dev-fpc/libasync ebuild dev-fpc/libasync ebuild
Created attachment 50014 [details] dev-fpc/pthreads ebuild dev-fpc/pthreads ebuild
Created attachment 50015 [details] dev-fpc/pasjpeg ebuild dev-fpc/pasjpeg ebuild
Created attachment 50016 [details] dev-fpc/ibase ebuild dev-fpc/ibase ebuild
Created attachment 50017 [details] dev-fpc/postgres ebuild dev-fpc/postgres ebuild
Created attachment 50018 [details] dev-fpc/mysql ebuild dev-fpc/mysql ebuild
Created attachment 50019 [details] dev-fpc/odbc ebuild dev-fpc/odbc ebuild
Created attachment 50020 [details] dev-fpc/sqlite ebuild dev-fpc/sqlite ebuild
Created attachment 50021 [details] dev-fpc/fcl ebuild dev-fpc/fcl ebuild
Created attachment 50022 [details] dev-fpc/regexpr ebuild dev-fpc/regexpr ebuild
Is cp in fileutils or coreutils ??
Created attachment 51353 [details] dev-lang/fpc/files : 50fpc containing an environment variable for fpc
Created attachment 51357 [details] fpc eclass, fpcmake fixes fpcmake fixes (removed -Tlinux since now invalid)
Created attachment 51366 [details] fpc compiler ebuild, put into dev-lang/fpc depend on sys-apps/coreutils not on fileutils anymore
Created attachment 51367 [details] fpc eclass, replace fileutils by coreutils replace fileutils by coreutils in DEPEND
Created attachment 51377 [details] dev-fpc/gtk2
Created attachment 51378 [details] dev-fpc/x11
Created attachment 51406 [details] fpc compiler ebuild, put into dev-lang/fpc fixed typo in PDEPEND
Created attachment 51693 [details] dev-lang/fpc/files/rtl-Package.fpc For base packages, the Package.fpc cannot be created by fpc itself since the fpcmake utility (which created Package.fpc usually) needs those libs to function at all. Hence put *-Package.fpc hardcoded for base packages
Created attachment 51694 [details] dev-fpc/fcl/files/Package.fpc ditto
Created attachment 51696 [details] dev-fpc/pthreads/files/Package.fpc ditto
Created attachment 51698 [details] dev-fpc/paszlib/files/Package.fpc ditto
Created attachment 51700 [details] dev-fpc/pasjpeg/files/Package.fpc ditto
Created attachment 51701 [details] dev-fpc/libasync/files/Package.fpc ditto
Created attachment 51703 [details] dev-fpc/netdb/files/Package.fpc ditto
Created attachment 51704 [details] dev-fpc/odbc/files/Package.fpc ditto
Created attachment 51705 [details] dev-fpc/mysql/files/Package.fpc ditto
Created attachment 51706 [details] dev-fpc/ibase/files/Package.fpc ditto
Created attachment 51707 [details] dev-fpc/postgres/files/Package.fpc ditto
Created attachment 51708 [details] dev-fpc/sqlite/files/Package.fpc ditto
version bump to 1.9.9 needed, soon 2.0. *Package.fpc need to be modified
Created attachment 52678 [details] fpc eclass, auto-fix Package.fpc version add automatic version= fixing of Package.fpc
Created attachment 52679 [details] fpc compiler ebuild, put into dev-lang/fpc auto-fix Package.fpc "version="
Created attachment 53095 [details] fpc compiler ebuild, put into dev-lang/fpc fix typo
Created attachment 54601 [details] dev-lang/fpc ebuild fix typo (missing category for fcl PDEPEND)
I do not think splitting it makes much sense. FPC is rather small (Takes less then 5 minutes to compile) and it is a mess when it comes to dependencies between the sub-packages. Splitting it would result in a huge amount of additional work. If noone is still working on this bug, one might consider closing this one and #79985
We have stable releases and hardly the ressources to maintain what we have in Portage already.