Definitely want feedback on this

General
1

<https://xojo.com/issue/48464>

Does anyone use the “obsolete” files ?
Maybe we should just delete them ?

Thoughts welcome folks

2

We use git repositories and so we just delete these obsolete files. If we have to recover a file, we fetch it from the last commit.

It would be great if these files were no longer created.

3

Deleting the obsolete files would be helpful. If anyone needs them, could that just be an IDE preference?

4

I ignore them in git. But they are sometimes filling the repsitory with useless files.
They are files that have recent changes in them right?

5

I think they should be removed automatically (or simply not created) as well.

Providing a selectable pref is fine as well if there are those who want them

6

I delete them. In fact, I wrote a script that I can invoke through SourceTree to do it so I’d be happy to save that step.

7

I wrote an Automator script to delete them, an IDE option not to create them would be quite beneficial.

8

[quote=337324:@Derk Jochems]I ignore them in git. But they are sometimes filling the repsitory with useless files.
They are files that have recent changes in them right?[/quote]
Obsolete ones can arise from

  • ones that represent an item that has been deleted from a project
  • files that are inside an item that has been renamed ie/ renaming a module that contains classes may cause this
  • project items you’ve moved so the on disk location also moves

Those are the only ones I can think of off the top of my head

9

Why not throw this open to the population at large?

10

[quote=337325:@Steve Upton]I think they should be removed automatically (or simply not created) as well.

Providing a selectable pref is fine as well if there are those who want them[/quote]

The case asks for a pref but so far I’m seeing that no one really needs or uses them

Moved to General

11

They should move to the trash.

12

Pro-tip: You can add *.obsolete to your .gitignore file.

13

+1 for deleting them when the Project is saved.

14

Delete! :slight_smile:

15

and which one is the situation where we get these?

  • several .rbvcp projects in the same root folder (in order to share classes/modules/… between those projects)
  • work in Project A
  • add Class 'NewClass" to .rbvcp project A
  • save Project A
  • open Project B
  • drop File “NewClass” into Project B
  • save Project B
    then we most of the time get an “obsolete” “NewClass - file”, but the contents match 100% to the “not obsolete” one.

anyway, back to your question: we delete those files, too. manually. every time.
I’ve never ever used (or had to use) an .obsolete file. it’s not likely when there is a source control being used.

16

I delete them manually every time. Never had a use for one of them.

17

ok looks like the consensus is to nuke them - so we will in a future release
should it pose any troubles we can revert this change

18

You can get an obsolete file from any one of the situation I listed

19

Never used one.

20

Nope. Used to delete them, now I use a git ignore. Nothing but noise to me.