Closed GoogleCodeExporter closed 9 years ago
Original comment by tim.lebe...@gmail.com
on 8 Feb 2011 at 8:58
Original comment by tim.lebe...@gmail.com
on 8 Feb 2011 at 9:17
Issue 29 has been merged into this issue.
Original comment by tim.lebe...@gmail.com
on 1 Mar 2011 at 6:52
a possible implementation (by Isaac):
It will be very nice to have a meta-package:
A package that only have a list of other programs, so you can install all yours
programs with one click.
Original comment by tim.lebe...@gmail.com
on 1 Mar 2011 at 6:53
as we have already 4 votes here maybe somebody would like to describe his
actual use case. Why do you want to export a list of applications and how would
you use it?
Original comment by tim.lebe...@gmail.com
on 3 Mar 2011 at 9:04
OK, I will try, but my English are not so good. If you install a new windows,
It will be very nice to have a list of all the software you use and to install
the whole list with one click. So in Linux you can make a "metapackage" that
make it. It is very useful. I have a list of all the program that use and I cat
install a new Linux very quickly.
I was for a sort time on a project that make some similar as a website:
http://en.communtu.org. So one can understand the idea of meta-package or
software-list.
Original comment by puchr...@gmail.com
on 3 Mar 2011 at 9:38
Original comment by tim.lebe...@gmail.com
on 15 Oct 2011 at 7:00
My main use case is servers. I have a set of applications I currently manually
install (and keep up-to-date) on each of them, such as Process Explorer and
Wireshark. Being able to import such a profile and having all of them installed
in a batch would be great. If I were to later add another app to that profile
and import it again, it should recognize the ones it already has and install
the new one. (As for removals, that's debatable.)
Original comment by chucker...@gmail.com
on 16 Oct 2011 at 9:49
I'll describe 2 simple solutions that work *now* in the following comments.
Please ignore. Testing code highlighting:
{{{
<test>
<test2></test2>
</test>
}}}
Original comment by tim.lebe...@gmail.com
on 17 Oct 2011 at 4:57
1st solution. This is what puchrojo@gmail.com talked about.
Save the following content in a file named MyProgs.xml and make it available
via http://www.yourcompanyhere.com/MyProgs.xml. Add the URL to the list of your
repositories in Npackd and try to install the super-package. All 4 packages
will be installed: Firefox, Thunderbird, VLC and the super-package. Please
modify the list of dependencies as you wish.
Here is the file content:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<spec-version>2</spec-version>
<package name="com.example.MyPrograms">
<title>Super-package for my programs</title>
</package>
<version name="1" package="com.example.MyPrograms" type="one-file">
<url>http://www.example.com/index.html</url>
<dependency package="org.mozilla.Firefox" versions="[7, 8)"/>
<dependency package="org.mozilla.Thunderbird" versions="[7, 8)"/>
<dependency package="com.videolan.VLCMediaPlayer" versions="[1.1.11, 1.1.11]"/>
</version>
</root>
Original comment by tim.lebe...@gmail.com
on 17 Oct 2011 at 5:17
2nd solution. Batch files.
Install NpackdCL. Save the following text in a file named MyProgs.bat and run
it as administrator. Note that you can also uninstall the packages if you
replace "add" with "remove"
"%npackd_cl%\npackdcl.exe" add --package=org.mozilla.Firefox --version=7.0.1
"%npackd_cl%\npackdcl.exe" add --package=org.mozilla.Thunderbird --version=7.0.1
"%npackd_cl%\npackdcl.exe" add --package=com.videolan.VLCMediaPlayer
--version=1.1.11
Original comment by tim.lebe...@gmail.com
on 17 Oct 2011 at 5:24
Hi Tim,
Thanks for pointing out those workarounds. I was thinking about the batch
option but for my use case, I prefer the super package.
Here are the use cases I can think of:
- private user: I reinstalled my machine and quickly want to reinstall by basic set of software. Ideally, I would love to be able to flag software/versions as favorites and then export the list.
- business user: I would like to provide my team with a set of software to install. They can load the list and install them all.
I agree that the super package option does the trick but ONLY if you implement
the ability to have LOCAL (ie local filesystem vs webserver) repositories.
I voted :)
Original comment by chev...@gmail.com
on 1 Nov 2012 at 12:07
The super package option works great but watch out for the typos in Tim´s
sample.
WRONG: versions="[7, 8)"/>
CORRECT: versions="[7, 8]"/>
The versions are like [min, max] with square brackets.
Original comment by chev...@gmail.com
on 1 Nov 2012 at 7:34
Note that UNinstalling a super package does NOT uninstall the dependencies.
Original comment by chev...@gmail.com
on 1 Nov 2012 at 7:35
"[7,8)" is not a mistake. "[" means "inclusive", "(" means "exclusive".
"[7,8)" means "any version between 7 and 8, but not 8.
7.99999 is OK, but 8 would not match
Original comment by tim.lebe...@gmail.com
on 3 Nov 2012 at 12:26
Ok, that explains why [6,6) did not work whereas [6,6] works. Thanks for
pointing out.
Original comment by chev...@gmail.com
on 3 Nov 2012 at 12:39
Issue 242 has been merged into this issue.
Original comment by tim.lebe...@gmail.com
on 21 May 2013 at 5:57
BTW, anybody can create a (super) package now on https://npackd.appspot.com
Original comment by tim.lebe...@gmail.com
on 27 Oct 2013 at 9:17
this is in my opinion fixed. See my previous comment. Let me know if you
disagree.
Original comment by tim.lebe...@gmail.com
on 29 Oct 2013 at 8:02
Original comment by tim.lebe...@gmail.com
on 13 Nov 2013 at 8:04
Original issue reported on code.google.com by
tim.lebe...@gmail.com
on 8 Feb 2011 at 8:50