pkg_add feature proposal
Hi everyone, I've just got an Idea (maybe others had it too?). When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ dependent packages exists and checksums are ok (after downloaded if with -r), etc. checks _before_ installing the packages, because if you get 3-4 packages broken/missing when one package depends on 30-40 (X apps etc.) you should delete all already installed... I've got this problem when did pkg_add -r mod_musicindex and for some reason mod_musicindex didn't build the flac and libogg when $> make package-recursive specified. When the pkg_add get to these packages and they were not found on the web server, I've had to delete all installed packages by hand... uhh... so, what would you say about that? thanks! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_add feature proposal
On Mon, Aug 25, 2008 at 02:37:16PM +0300, Anton - Valqk wrote: > Hi everyone, > > I've just got an Idea (maybe others had it too?). > > When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ > dependent packages exists and checksums are ok (after downloaded if with > -r), etc. checks _before_ installing the packages, because if you get > 3-4 packages broken/missing when one package depends on 30-40 (X apps > etc.) you should delete all already installed... > > I've got this problem when did pkg_add -r mod_musicindex and for some > reason mod_musicindex didn't build the flac and libogg when > $> make package-recursive > specified. > When the pkg_add get to these packages and they were not found on the > web server, I've had to delete all installed packages by hand... uhh... > > so, what would you say about that? I'd say it's a great idea (and an ideal idea), but it's not easily implementable. Where would pkg_add get its list of dependencies from? The port Makefile? And what if the user doesn't have ports installed? This is one of the many quirks of the ports vs. package system. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_add feature proposal
On Mon, Aug 25, 2008 at 05:48:06AM -0700, Jeremy Chadwick wrote: > On Mon, Aug 25, 2008 at 02:37:16PM +0300, Anton - Valqk wrote: > > Hi everyone, > > > > I've just got an Idea (maybe others had it too?). > > > > When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ > > dependent packages exists and checksums are ok (after downloaded if with > > -r), etc. checks _before_ installing the packages, because if you get > > 3-4 packages broken/missing when one package depends on 30-40 (X apps > > etc.) you should delete all already installed... > > > > I've got this problem when did pkg_add -r mod_musicindex and for some > > reason mod_musicindex didn't build the flac and libogg when > > $> make package-recursive > > specified. > > When the pkg_add get to these packages and they were not found on the > > web server, I've had to delete all installed packages by hand... uhh... > > > > so, what would you say about that? > > I'd say it's a great idea (and an ideal idea), but it's not easily > implementable. Where would pkg_add get its list of dependencies from? > The port Makefile? And what if the user doesn't have ports installed? > > This is one of the many quirks of the ports vs. package system. Well, pkg_add *already* gets the list of dependencies from the .tbz file that it is either passed on the command line or it downloads. I believe that Anton is asking for a bit more separation between the "fetch all packages to be installed" and the "install all fetched (fought?) packages" phases of pkg_add's operation. However, given the way that pkg_add operates by invoking itself recursively, it might not be easy to do this without a major rewrite and algorithm change. G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 No language can express every thought unambiguously, least of all this one. pgpUuzGObLGgm.pgp Description: PGP signature
Re: pkg_add feature proposal
On Mon, Aug 25, 2008 at 8:37 AM, Anton - Valqk <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I've just got an Idea (maybe others had it too?). > > When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ > dependent packages exists and checksums are ok (after downloaded if with > -r), etc. checks _before_ installing the packages, because if you get > 3-4 packages broken/missing when one package depends on 30-40 (X apps > etc.) you should delete all already installed... > > I've got this problem when did pkg_add -r mod_musicindex and for some > reason mod_musicindex didn't build the flac and libogg when > $> make package-recursive > specified. > When the pkg_add get to these packages and they were not found on the > web server, I've had to delete all installed packages by hand... uhh... > > so, what would you say about that? Be warned that large packages and/or packages that depend on large packages may lead to a full /var/tmp if that filesystem is not large enough. OpenOffice, JDK and teTeX are good examples. I had this problem on Ubuntu some time ago. -- cd /usr/ports/sysutils/life make clean ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_add feature proposal
Peter Pentchev wrote: On Mon, Aug 25, 2008 at 05:48:06AM -0700, Jeremy Chadwick wrote: On Mon, Aug 25, 2008 at 02:37:16PM +0300, Anton - Valqk wrote: Hi everyone, I've just got an Idea (maybe others had it too?). When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ dependent packages exists and checksums are ok (after downloaded if with -r), etc. checks _before_ installing the packages, because if you get 3-4 packages broken/missing when one package depends on 30-40 (X apps etc.) you should delete all already installed... I've got this problem when did pkg_add -r mod_musicindex and for some reason mod_musicindex didn't build the flac and libogg when $> make package-recursive specified. When the pkg_add get to these packages and they were not found on the web server, I've had to delete all installed packages by hand... uhh... so, what would you say about that? I'd say it's a great idea (and an ideal idea), but it's not easily implementable. Where would pkg_add get its list of dependencies from? The port Makefile? And what if the user doesn't have ports installed? This is one of the many quirks of the ports vs. package system. Well, pkg_add *already* gets the list of dependencies from the .tbz file that it is either passed on the command line or it downloads. I believe that Anton is asking for a bit more separation between the "fetch all packages to be installed" and the "install all fetched (fought?) packages" phases of pkg_add's operation. However, given the way that pkg_add operates by invoking itself recursively, it might not be easy to do this without a major rewrite and algorithm change. I don't think it would be that hard to do. The root package has a complete list of its dependencies in +CONTENTS, and they are even listed in the order they need to be installed (so if it is recursive, it will only be to one level). And it is a good idea. So the only question is "who will do it." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_add feature proposal
On Mon, Aug 25, 2008 at 09:22:57AM -0500, Stephen Montgomery-Smith wrote: > Peter Pentchev wrote: > > On Mon, Aug 25, 2008 at 05:48:06AM -0700, Jeremy Chadwick wrote: > >> On Mon, Aug 25, 2008 at 02:37:16PM +0300, Anton - Valqk wrote: > >>> Hi everyone, > >>> > >>> I've just got an Idea (maybe others had it too?). > >>> > >>> When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ > >>> dependent packages exists and checksums are ok (after downloaded if with > >>> -r), etc. checks _before_ installing the packages, because if you get > >>> 3-4 packages broken/missing when one package depends on 30-40 (X apps > >>> etc.) you should delete all already installed... > >>> > >>> I've got this problem when did pkg_add -r mod_musicindex and for some > >>> reason mod_musicindex didn't build the flac and libogg when > >>> $> make package-recursive > >>> specified. > >>> When the pkg_add get to these packages and they were not found on the > >>> web server, I've had to delete all installed packages by hand... uhh... > >>> > >>> so, what would you say about that? > >> I'd say it's a great idea (and an ideal idea), but it's not easily > >> implementable. Where would pkg_add get its list of dependencies from? > >> The port Makefile? And what if the user doesn't have ports installed? > >> > >> This is one of the many quirks of the ports vs. package system. > > > > Well, pkg_add *already* gets the list of dependencies from the .tbz file > > that it is either passed on the command line or it downloads. I believe > > that Anton is asking for a bit more separation between the "fetch all > > packages to be installed" and the "install all fetched (fought?) packages" > > phases of pkg_add's operation. However, given the way that pkg_add > > operates by invoking itself recursively, it might not be easy to do this > > without a major rewrite and algorithm change. > > > > I don't think it would be that hard to do. The root package has a > complete list of its dependencies in +CONTENTS, and they are even listed > in the order they need to be installed (so if it is recursive, it will > only be to one level). > > And it is a good idea. So the only question is "who will do it." Not that I'm volunteering to do it, but I've run into the need to use pkg_fetch and had to install portupgrade just to get it. What we are discussing here is closely related to that. It wouldn't be a hard stretch to implement a pkg_fetch in the base. It's on my todo list but not sure when (if) I will ever get to it. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_add feature proposal
Uh-oh, totally forgot about this post :( It'd be great to see that implemented, and it's nice to see that other ppl are seeing point in having this option. The bad thing is that I'm not that familiar with pkg_* and ports internals and would be very time consuming for me to implement it... of course it'd be great to see the internals of these two but unfortunately at the very moment really no time to do this. About getting out of disk space - well, the packages are not stream and are with known size. Meaning disk space calcs can be made to warn you about this, and if you install *big* packages 100 and more in a list you *definitely* don't want to get stuck in the middle of installing them (and not having a way to 'rollback') This could be an option (enabled by default tough)... Another nice idea that came to me is to have a util (ot automated check after pkg_add -r and installing is finished) to see if _all_ the files from the package are installed in proper place and match md5sums in +CONTENTS - I often get packages (from my custom build server) that for some reason don't install _all_ files from +CONTENTS and I see this when I try to access a file or delete the package (typical example: pkg_add -r apache22 and I have no /usr/local/etc/rc.d/apache22 script?!?!) cheers, valqk. Carlos A. M. dos Santos wrote: > On Mon, Aug 25, 2008 at 8:37 AM, Anton - Valqk <[EMAIL PROTECTED]> wrote: > >> Hi everyone, >> >> I've just got an Idea (maybe others had it too?). >> >> When doing pkg_add [-r] wouldn't it be better if pkg_add checks if _all_ >> dependent packages exists and checksums are ok (after downloaded if with >> -r), etc. checks _before_ installing the packages, because if you get >> 3-4 packages broken/missing when one package depends on 30-40 (X apps >> etc.) you should delete all already installed... >> >> I've got this problem when did pkg_add -r mod_musicindex and for some >> reason mod_musicindex didn't build the flac and libogg when >> $> make package-recursive >> specified. >> When the pkg_add get to these packages and they were not found on the >> web server, I've had to delete all installed packages by hand... uhh... >> >> so, what would you say about that? >> > > Be warned that large packages and/or packages that depend on large > packages may lead to a full /var/tmp if that filesystem is not large > enough. OpenOffice, JDK and teTeX are good examples. I had this > problem on Ubuntu some time ago. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
