Bug 19586 – Ebuild for Perforce SCM

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description leon j. breedt 2003-04-18 20:17:20 UTC]

I've created an ebuild for the Perforce Fast SCM. Its files are distributed in
binary format only, and the Linux executables for architectures other than ~x86
look quite outdated, so it currently supports x86 only.

The licensing is unique, and will require a new license file called 'Perforce'.


Reproducible: Always
Steps to Reproduce:

[Comment 1 leon j. breedt 2003-04-18 20:19:23 UTC]

Created attachment 10854 [details]
dev-util/perforce directory

[Comment 2 leon j. breedt 2003-04-18 20:20:27 UTC]

Created attachment 10855 [details]
Perforce license file for /usr/portage/licenses

[Comment 3 leon j. breedt 2003-04-18 20:24:00 UTC]

little bug in .ebuild...DEPEND= should technically be RDEPEND=.

[Comment 4 Stuart Herbert (RETIRED) 2003-10-01 02:00:25 UTC]

Hi!

Sorry it's taken so long, but I've finally committed a modified version of
your ebuild into Portage.  Could you please test it, and let me know how
you get on?

Thanks,
Stu

[Comment 5 ben calvert 2003-10-26 12:54:17 UTC]

Created attachment 19824 [details]
init.d script

this is a hacked version of the init script to work around the problem that
start-stop-daemon in suid mode tries to write the pidfile after going setuid
perforce:perforce, and fails

[Comment 6 ben calvert 2003-10-26 12:57:05 UTC]

Created attachment 19825 [details]
ebuild for 2003.1 ( x86 only ) version

ebuild for the newer version (still x86 only).	Hopefully, i'll figure out
how
to get the rpm-packaged gui to install too and add that in.

[Comment 7 ben calvert 2003-10-26 13:05:22 UTC]

have added ebuild for newer version ( still x86 only ) and an ugly hack of
an init script to work around what is either my lack of understanding, or
an annoying feature of the stop-start-daemon ( after going suid, can't write
the pidfile to /var/run )

[Comment 8 ben calvert 2003-10-26 15:13:13 UTC]

Created attachment 19832 [details]
ebuild for 2003.1, with gui.  still ~x86 only

have added steps to install the gui.

[Comment 9 ben calvert 2003-10-26 15:30:34 UTC]

Created attachment 19834 [details]
perforce SCM, with GUI, x86 only

forgot it depends on rpm2targz

[Comment 10 ben calvert 2003-10-26 17:58:36 UTC]

Created attachment 19837 [details]
ebuild for 2003.1, with gui.  still ~x86 only

use rpm eclass, fix creation of /var/log/perforce

[Comment 11 ben calvert 2003-10-26 18:34:39 UTC]

Created attachment 19838 [details]
ebuild for 2003.1, with gui.  still ~x86 only

I suck :)  fixed the rpm eclass useage so that the contents actually get
installed

[Comment 12 Stuart Herbert (RETIRED) 2003-11-24 14:48:55 UTC]

Hi Ben,

I'll take a look at your ebuild before the end of the week, and commit it if I like the look of it.

Thanks,
Stu

[Comment 13 Stuart Herbert (RETIRED) 2003-11-26 14:48:06 UTC]

Okay.  I've had a look, and I'm thinking of breaking up perforce into three separate packages:

perforce-server: the perforce daemon
perforce-cli: the command-line tools
perforce-gui: the new gui

My thinking is that some people will want the CLI tools without a local copy of the perforce daemon.  Also, not everyone will want the gui.

Let me know what you think,
Stu

[Comment 14 Stuart Herbert (RETIRED) 2003-12-14 02:05:29 UTC]

I've added the following packages to Portage:

* perforce-cli
* perforce-gui
* perforce-proxy

The perforce package now installs just the p4d, p4ftpd and p4web programs.

Best regards,
Stu