home.social

#perforce — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #perforce, aggregated by home.social.

  1. #Linux #gamedev update:

    Life has been a nightmare the past couple months so not much time to make progress. I've been working on automation to easily set up the environment and tools we need on new machines/VMs, including tools that lack proper Linux installers (I'm looking at you #Perforce).

    I'm convinced Kubuntu, but with Snap removed and Flatpak added, is the best environment for converts. I wish there was a distro that was this out of the box.

  2. #Linux #gamedev update:

    Life has been a nightmare the past couple months so not much time to make progress. I've been working on automation to easily set up the environment and tools we need on new machines/VMs, including tools that lack proper Linux installers (I'm looking at you #Perforce).

    I'm convinced Kubuntu, but with Snap removed and Flatpak added, is the best environment for converts. I wish there was a distro that was this out of the box.

  3. #Linux #gamedev update:

    Life has been a nightmare the past couple months so not much time to make progress. I've been working on automation to easily set up the environment and tools we need on new machines/VMs, including tools that lack proper Linux installers (I'm looking at you #Perforce).

    I'm convinced Kubuntu, but with Snap removed and Flatpak added, is the best environment for converts. I wish there was a distro that was this out of the box.

  4. #Linux #gamedev update:

    Life has been a nightmare the past couple months so not much time to make progress. I've been working on automation to easily set up the environment and tools we need on new machines/VMs, including tools that lack proper Linux installers (I'm looking at you #Perforce).

    I'm convinced Kubuntu, but with Snap removed and Flatpak added, is the best environment for converts. I wish there was a distro that was this out of the box.

  5. #Linux #gamedev update:

    Life has been a nightmare the past couple months so not much time to make progress. I've been working on automation to easily set up the environment and tools we need on new machines/VMs, including tools that lack proper Linux installers (I'm looking at you #Perforce).

    I'm convinced Kubuntu, but with Snap removed and Flatpak added, is the best environment for converts. I wish there was a distro that was this out of the box.

  6. Не Git-ом единым: гид по системам контроля версий для особых случаев

    А есть ли жизнь вне GIT? Что там? Может там летают птеродактили или НЛО? Или там просто пустое поле? Давайте разбираться.

    habr.com/ru/articles/984556/

    #Git #Mercurial #Subversion #Perforce #Darcs #Pijul

  7. Не Git-ом единым: гид по системам контроля версий для особых случаев

    А есть ли жизнь вне GIT? Что там? Может там летают птеродактили или НЛО? Или там просто пустое поле? Давайте разбираться.

    habr.com/ru/articles/984556/

    #Git #Mercurial #Subversion #Perforce #Darcs #Pijul

  8. Не Git-ом единым: гид по системам контроля версий для особых случаев

    А есть ли жизнь вне GIT? Что там? Может там летают птеродактили или НЛО? Или там просто пустое поле? Давайте разбираться.

    habr.com/ru/articles/984556/

    #Git #Mercurial #Subversion #Perforce #Darcs #Pijul

  9. Не Git-ом единым: гид по системам контроля версий для особых случаев

    А есть ли жизнь вне GIT? Что там? Может там летают птеродактили или НЛО? Или там просто пустое поле? Давайте разбираться.

    habr.com/ru/articles/984556/

    #Git #Mercurial #Subversion #Perforce #Darcs #Pijul

  10. More #Linux progress: VCS

    #Perforce has their own apt repository and the CLI tools install and work great. Not a surprise; it's common practice to host P4 depots on Linux hosts.

    The GUI tools exist and fully function, so A+ there. Unfortunately they aren't in their apt repo, only as a tarball download of bins requiring fully manual install. Default (Light) theme had issues, but the dark theme is fine, and no one should ever use light themes. ;)

    I've reached out to them about both issues.

  11. More #Linux progress: VCS

    #Perforce has their own apt repository and the CLI tools install and work great. Not a surprise; it's common practice to host P4 depots on Linux hosts.

    The GUI tools exist and fully function, so A+ there. Unfortunately they aren't in their apt repo, only as a tarball download of bins requiring fully manual install. Default (Light) theme had issues, but the dark theme is fine, and no one should ever use light themes. ;)

    I've reached out to them about both issues.

  12. More #Linux progress: VCS

    #Perforce has their own apt repository and the CLI tools install and work great. Not a surprise; it's common practice to host P4 depots on Linux hosts.

    The GUI tools exist and fully function, so A+ there. Unfortunately they aren't in their apt repo, only as a tarball download of bins requiring fully manual install. Default (Light) theme had issues, but the dark theme is fine, and no one should ever use light themes. ;)

    I've reached out to them about both issues.

  13. By far the biggest issue I've encountered with #godot so far is that it doesn't support working in a #perforce workspace.

    I'm sure people here will want to reply with a FOSS rant, but the truth is to become a major #gamedev tool you need to support p4; it is what 90% of the industry uses, and for good reason.

    Git is absolutely terrible at handling large/binary files (which was an intentional design decision).

  14. By far the biggest issue I've encountered with #godot so far is that it doesn't support working in a #perforce workspace.

    I'm sure people here will want to reply with a FOSS rant, but the truth is to become a major #gamedev tool you need to support p4; it is what 90% of the industry uses, and for good reason.

    Git is absolutely terrible at handling large/binary files (which was an intentional design decision).

  15. By far the biggest issue I've encountered with #godot so far is that it doesn't support working in a #perforce workspace.

    I'm sure people here will want to reply with a FOSS rant, but the truth is to become a major #gamedev tool you need to support p4; it is what 90% of the industry uses, and for good reason.

    Git is absolutely terrible at handling large/binary files (which was an intentional design decision).

  16. By far the biggest issue I've encountered with #godot so far is that it doesn't support working in a #perforce workspace.

    I'm sure people here will want to reply with a FOSS rant, but the truth is to become a major #gamedev tool you need to support p4; it is what 90% of the industry uses, and for good reason.

    Git is absolutely terrible at handling large/binary files (which was an intentional design decision).

  17. By far the biggest issue I've encountered with #godot so far is that it doesn't support working in a #perforce workspace.

    I'm sure people here will want to reply with a FOSS rant, but the truth is to become a major #gamedev tool you need to support p4; it is what 90% of the industry uses, and for good reason.

    Git is absolutely terrible at handling large/binary files (which was an intentional design decision).

  18. When versions of critical infrastructure applications go EOL the battle is always to consider the risk of the upgrade vs the risk of staying where you are without support. If you have an older version of Puppet and are thinking of upgrading to Puppet 8, you should have a watch of this new video from Stephen Potter as he tackles some key upgrade tips!

    youtube.com/watch?v=EB2Ws6YtgOs

  19. When versions of critical infrastructure applications go EOL the battle is always to consider the risk of the upgrade vs the risk of staying where you are without support. If you have an older version of #Perforce Puppet and are thinking of upgrading to Puppet 8, you should have a watch of this new video from Stephen Potter as he tackles some key upgrade tips!

    youtube.com/watch?v=EB2Ws6YtgOs

    #sre #devops

  20. When versions of critical infrastructure applications go EOL the battle is always to consider the risk of the upgrade vs the risk of staying where you are without support. If you have an older version of #Perforce Puppet and are thinking of upgrading to Puppet 8, you should have a watch of this new video from Stephen Potter as he tackles some key upgrade tips!

    youtube.com/watch?v=EB2Ws6YtgOs

    #sre #devops

  21. When versions of critical infrastructure applications go EOL the battle is always to consider the risk of the upgrade vs the risk of staying where you are without support. If you have an older version of #Perforce Puppet and are thinking of upgrading to Puppet 8, you should have a watch of this new video from Stephen Potter as he tackles some key upgrade tips!

    youtube.com/watch?v=EB2Ws6YtgOs

    #sre #devops

  22. When versions of critical infrastructure applications go EOL the battle is always to consider the risk of the upgrade vs the risk of staying where you are without support. If you have an older version of #Perforce Puppet and are thinking of upgrading to Puppet 8, you should have a watch of this new video from Stephen Potter as he tackles some key upgrade tips!

    youtube.com/watch?v=EB2Ws6YtgOs

    #sre #devops

  23. A little sneak peek by Product Leader Margaret Lee on the new Infra Assistant coming to @puppet is now on the Puppet YouTube channel! This makes it easier to get data about your infrastructure without needing to learn the query language to run against your APIs.

    #DevOps #PerforcePuppet #Perforce #Puppet

    youtube.com/watch?v=FiVnAHbwdnI

  24. A little sneak peek by Product Leader Margaret Lee on the new Infra Assistant coming to @puppet is now on the Puppet YouTube channel! This makes it easier to get data about your infrastructure without needing to learn the query language to run against your APIs.

    #DevOps #PerforcePuppet #Perforce #Puppet

    youtube.com/watch?v=FiVnAHbwdnI

  25. A little sneak peek by Product Leader Margaret Lee on the new Infra Assistant coming to @puppet is now on the Puppet YouTube channel! This makes it easier to get data about your infrastructure without needing to learn the query language to run against your APIs.

    #DevOps #PerforcePuppet #Perforce #Puppet

    youtube.com/watch?v=FiVnAHbwdnI

  26. A little sneak peek by Product Leader Margaret Lee on the new Infra Assistant coming to @puppet is now on the Puppet YouTube channel! This makes it easier to get data about your infrastructure without needing to learn the query language to run against your APIs.

    #DevOps #PerforcePuppet #Perforce #Puppet

    youtube.com/watch?v=FiVnAHbwdnI

  27. A little sneak peek by Product Leader Margaret Lee on the new Infra Assistant coming to @puppet is now on the Puppet YouTube channel! This makes it easier to get data about your infrastructure without needing to learn the query language to run against your APIs.

    #DevOps #PerforcePuppet #Perforce #Puppet

    youtube.com/watch?v=FiVnAHbwdnI

  28. If you’re the one who gets CVE alerts and has to convince others to take them seriously, this whitepaper might help. It has some with stats and positioning that can support your case for prioritizing vulnerability management.

    Yeah, there’s a bit about how #Perforce #Puppet can help at the end, but there are good business case things on MTTR and breach risks too. Some links in there to some supporting reports from other sources, as well.

    #DevSecOps #Cybersecurity

    puppet.com/resources/vulnerabi

  29. If you’re the one who gets CVE alerts and has to convince others to take them seriously, this whitepaper might help. It has some with stats and positioning that can support your case for prioritizing vulnerability management.

    Yeah, there’s a bit about how #Perforce #Puppet can help at the end, but there are good business case things on MTTR and breach risks too. Some links in there to some supporting reports from other sources, as well.

    #DevSecOps #Cybersecurity

    puppet.com/resources/vulnerabi

  30. If you’re the one who gets CVE alerts and has to convince others to take them seriously, this whitepaper might help. It has some with stats and positioning that can support your case for prioritizing vulnerability management.

    Yeah, there’s a bit about how #Perforce #Puppet can help at the end, but there are good business case things on MTTR and breach risks too. Some links in there to some supporting reports from other sources, as well.

    #DevSecOps #Cybersecurity

    puppet.com/resources/vulnerabi

  31. If you’re the one who gets CVE alerts and has to convince others to take them seriously, this whitepaper might help. It has some with stats and positioning that can support your case for prioritizing vulnerability management.

    Yeah, there’s a bit about how #Perforce #Puppet can help at the end, but there are good business case things on MTTR and breach risks too. Some links in there to some supporting reports from other sources, as well.

    #DevSecOps #Cybersecurity

    puppet.com/resources/vulnerabi

  32. If you’re the one who gets CVE alerts and has to convince others to take them seriously, this whitepaper might help. It has some with stats and positioning that can support your case for prioritizing vulnerability management.

    Yeah, there’s a bit about how #Perforce #Puppet can help at the end, but there are good business case things on MTTR and breach risks too. Some links in there to some supporting reports from other sources, as well.

    #DevSecOps #Cybersecurity

    puppet.com/resources/vulnerabi

  33. Today's been one of those days where I wish we were using anything other than #perforce for version control. This thing is broken beyond belief. Working on several changelists? Sure, but don't create new files, shelving them and reverting the changelist doesn't remove the newly added file from the filesystem. Which breaks #ceedling's automatic test discovery. The work around is to rename the test_* file with some other prefix manually. It sucks.
    #versioncontrol

  34. Today's been one of those days where I wish we were using anything other than #perforce for version control. This thing is broken beyond belief. Working on several changelists? Sure, but don't create new files, shelving them and reverting the changelist doesn't remove the newly added file from the filesystem. Which breaks #ceedling's automatic test discovery. The work around is to rename the test_* file with some other prefix manually. It sucks.
    #versioncontrol

  35. Today's been one of those days where I wish we were using anything other than #perforce for version control. This thing is broken beyond belief. Working on several changelists? Sure, but don't create new files, shelving them and reverting the changelist doesn't remove the newly added file from the filesystem. Which breaks #ceedling's automatic test discovery. The work around is to rename the test_* file with some other prefix manually. It sucks.
    #versioncontrol