make package for ports, general question
in [Ports]
|
Prev: java in a browser (was: Re: [CFT] Firefox 3.6 for FreeBSD)
Next: TLS(and by extension all threading) completely broken inValgrind on i386/amd64
From: Jason on 25 Feb 2010 00:25 Hello All, I have been converting our internal packaging system from one system to ports, and have been very successful with it so far. Having lots of fun, as well, if that can be said of ports :) I think it can. So far I have 14! I am learning a lot about ports, and have managed to localize so much and finding how adaptable the system is. That being said, I ran into an item today that had me perplexed. Basically, it comes down to this: http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html Why is it that "make package" doesn't include the execution instructions noted in the Makefile. To me, with my new knowledge of the ports system, seems like double the work for development and maintaining a port and package. I'm not just speaking for someone that maintains internal ports, but the many developers that maintain ports in the official ports tree for FreeBSD. Is their a solution or patch out there that may take care of this, or a method for which I could adopt that would take out this seemingly extra step to support a binary package? My goal was to make sure everything worked under the ports tree for which I am creating, and I had assumed the that package structure would just follow suit. I see that assumption is wrong, now, but would be interested in exploring how others are handing internal ports trees and distribution to their different environments. Ideally, I would like to address the issue with the binary packages, as the ports tree adoption has been very successful. Thanks so much, Jason _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Ion-Mihai Tetcu on 25 Feb 2010 02:52 On Wed, 24 Feb 2010 21:25:06 -0800 Jason <jhelfman(a)e-e.com> wrote: [ .. ] > That being said, I ran into an item today that had me perplexed. > > Basically, it comes down to this: > http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html > > Why is it that "make package" doesn't include the execution > instructions noted in the Makefile. To me, with my new knowledge of > the ports system, seems like double the work for development and > maintaining a port and package. I'm not just speaking for someone > that maintains internal ports, but the many developers that maintain > ports in the official ports tree for FreeBSD. [ .. ] What exactly doesn't work for you? Are you talking about pkg-message? -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu(a)FreeBSD.org, PGP Key ID 057E9F8B493A297B
From: Dominic Fandrey on 25 Feb 2010 03:25 On 25/02/2010 06:25, Jason wrote: > That being said, I ran into an item today that had me perplexed. > > Basically, it comes down to this: > http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html > > Why is it that "make package" doesn't include the execution instructions > noted in the Makefile. To me, with my new knowledge of the ports system, > seems like double the work for development and maintaining a port and > package. ... It's not like that at all. You should only add stuff into the ports Makefile that installs new files into the system. Everything else, like creating groups and users, updating an index and so forth, should only be done in the pkg-install script. There is no redundancy. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Jason on 25 Feb 2010 10:52 On Thu, Feb 25, 2010 at 09:25:09AM +0100, Dominic Fandrey thus spake: >On 25/02/2010 06:25, Jason wrote: >> That being said, I ran into an item today that had me perplexed. >> >> Basically, it comes down to this: >> http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html >> >> Why is it that "make package" doesn't include the execution instructions >> noted in the Makefile. To me, with my new knowledge of the ports system, >> seems like double the work for development and maintaining a port and >> package. ... > >It's not like that at all. You should only add stuff into the ports >Makefile that installs new files into the system. > This make much more sense now. >Everything else, like creating groups and users, updating an index >and so forth, should only be done in the pkg-install script. > That's unfortunate for the user installation, as you can use the native USERS directive in Makefiles to install users. I've started using local UID and GID files to install users, and it has worked out rather well. I suppose removing the functionality from the Makefile, yet keeping those files up-to-date for reference, is still a good idea. Do: BINMODE SHAREMODE CHOWN CHMOD need to go into a pkg-install file? I saw that there is a "Do & Dont's" on the todo list at wiki.freebsd.org for Ports. Maybe adding some of this information in there would be good. >There is no redundancy. > Thank you for the explanation, Jason >-- >A: Because it fouls the order in which people normally read text. >Q: Why is top-posting such a bad thing? >A: Top-posting. >Q: What is the most annoying thing on usenet and in e-mail? > _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Dominic Fandrey on 25 Feb 2010 11:48
On 25/02/2010 16:52, Jason wrote: > On Thu, Feb 25, 2010 at 09:25:09AM +0100, Dominic Fandrey thus spake: >> On 25/02/2010 06:25, Jason wrote: >>> That being said, I ran into an item today that had me perplexed. >>> >>> Basically, it comes down to this: >>> http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html >>> >>> Why is it that "make package" doesn't include the execution instructions >>> noted in the Makefile. To me, with my new knowledge of the ports system, >>> seems like double the work for development and maintaining a port and >>> package. ... >> >> It's not like that at all. You should only add stuff into the ports >> Makefile that installs new files into the system. >> > > This make much more sense now. > >> Everything else, like creating groups and users, updating an index >> and so forth, should only be done in the pkg-install script. >> > > That's unfortunate for the user installation, as you can use the native > USERS directive in Makefiles to install users. I've started using local UID > and GID files to install users, and it has worked out rather well. I > suppose > removing the functionality from the Makefile, yet keeping those files > up-to-date for reference, is still a good idea. My error, USERS and GROUPS are official ports features and hence should be used. That kind of information also makes it into packages just fine. I don't maintain any ports that create users, so I overlooked it. Sorry for providing false information. > > Do: > > BINMODE > SHAREMODE > CHOWN > CHMOD > need to go into a pkg-install file? No, because the package is a tar archive that preserves these file properties. > I saw that there is a "Do & Dont's" on the todo list at wiki.freebsd.org > for > Ports. Maybe adding some of this information in there would be good. As you can see, the cases where a pkg-install script is actually needed are rather rare. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |