#49114 Clean source tree
Closed: wontfix 5 months ago by mreynolds. Opened 3 years ago by firstyear.

Our source tree is a bit of a mess. We have different server components all over the place, and sometimes we even have unrelated parts put together.

We should identify:

  • Scripts we no longer use
  • dead code
  • Code that can be broken into subfolders (ie libslapd, ns-slapd, )
  • Old binaries and code we don't use.

We should clean the source tree to make it easier and more accesible to find pieces, provide clarity as to what parts belong to what libraries, and what components serve what purpose.

This only affects our build and some patches, does not affect our API.


Metadata Update from @firstyear:
- Issue assigned to firstyear
- Issue set to the milestone: FUTURE

3 years ago

We are aware of this and will do so in steps, no need for a individual ticket

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 months ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2173

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata