HI All,
I had a look through most of the development hand books, but wanted to clarify a few things that I either missed, didn’t see or may have been left out of the documentation.
this kind of pain point stems from unpopular dealings with linux that have caused issues in the past .. I can't say this wont happen with freebsd but ideally Id like to find something to present.
Se lets address the issues.
dead/out-of-date or unmaintained packages
#1 - the dev team starts creating an application under linux .. one dev picks some libs, packages and other supporting 3rd party applications they are familiar with .. said team builds a package repo, adds all the 3rd party urls/codebases and "everything is awesome" . original developer sees something shiny and quits .. the rest of the dev team never notices that one of the 3rd party links is dead/no longer updating. (idk the 3rd party dev got board, or what ever) .. a few years go by and then .. boom .. the main application breaks because this old application is no longer supported / broken.. Dev team is now stuck trying to re-write, mangle or rehash their code to work around the problem. causing all sorts of issues..
Q:
? - if a committer stops updating code, how does the council determine when their code will be EOL'ed
? - how are consumers of that package notified or expected to know when a package they use will no longer be maintained or apart of the base
? - I "assume" all packages are rebuilt for each major release and checked for dependencies? is this correct?
? - What level of code review is done by the council? for example, some bsd teams will go through it literally line by line and if it sucks its rejected.
? - if there is a major issue with a package and a hot fix is applied, but the base version in stable/release is still on the older version. how do you deal with that? ie do you download it from current and compile for source? or is that included in the security patches etc.
#2 - if your application only relies on adding scripts, config and supporting components for 3rd party applications..
? - is it better to just package / mantiain your own code. ie use normal updates and pull down your repos from git via a configuration manager.. or
should you still go with your own complete repo and push from that?
? - as abouve if your required to mix binaries and compile the odd packag from source, how do you get around that? or is that even a problem in the first place?
thanks for your time, sorry if they seem trivial.. or I missed something obious in the documentaion.
I had a look through most of the development hand books, but wanted to clarify a few things that I either missed, didn’t see or may have been left out of the documentation.
this kind of pain point stems from unpopular dealings with linux that have caused issues in the past .. I can't say this wont happen with freebsd but ideally Id like to find something to present.
Se lets address the issues.
dead/out-of-date or unmaintained packages
#1 - the dev team starts creating an application under linux .. one dev picks some libs, packages and other supporting 3rd party applications they are familiar with .. said team builds a package repo, adds all the 3rd party urls/codebases and "everything is awesome" . original developer sees something shiny and quits .. the rest of the dev team never notices that one of the 3rd party links is dead/no longer updating. (idk the 3rd party dev got board, or what ever) .. a few years go by and then .. boom .. the main application breaks because this old application is no longer supported / broken.. Dev team is now stuck trying to re-write, mangle or rehash their code to work around the problem. causing all sorts of issues..
Q:
? - if a committer stops updating code, how does the council determine when their code will be EOL'ed
? - how are consumers of that package notified or expected to know when a package they use will no longer be maintained or apart of the base
? - I "assume" all packages are rebuilt for each major release and checked for dependencies? is this correct?
? - What level of code review is done by the council? for example, some bsd teams will go through it literally line by line and if it sucks its rejected.
? - if there is a major issue with a package and a hot fix is applied, but the base version in stable/release is still on the older version. how do you deal with that? ie do you download it from current and compile for source? or is that included in the security patches etc.
#2 - if your application only relies on adding scripts, config and supporting components for 3rd party applications..
? - is it better to just package / mantiain your own code. ie use normal updates and pull down your repos from git via a configuration manager.. or
should you still go with your own complete repo and push from that?
? - as abouve if your required to mix binaries and compile the odd packag from source, how do you get around that? or is that even a problem in the first place?
thanks for your time, sorry if they seem trivial.. or I missed something obious in the documentaion.
