On Tue, Jul 17, 2012 at 03:23:12AM -0300, Martin Cigorraga wrote:
> Hi guys!
>
> I was thinking it could be a cool feature if pacman can warn the user every
> time news are published on our main page by issuing an alert when:
> 1. issuing a pacman -Syu -- which involves full system upgrade
> 2. i
On Tue, Jul 17, 2012 at 11:50:26AM +1000, Allan McRae wrote:
> Detect a conflict between a file/symlink in one package and a directory
> in another when both are being installed at once.
>
> A side effect is the creation on conflicts between a direcotry symlink
> and a real directory (e.g lib -> u
Beautiful!
It definetely slipped under my radar, thanks =D
--
-msx
On 17/07/12 17:19, Lukas Fleischer wrote:
> On Tue, Jul 17, 2012 at 11:50:26AM +1000, Allan McRae wrote:
>> Detect a conflict between a file/symlink in one package and a directory
>> in another when both are being installed at once.
>>
>> A side effect is the creation on conflicts between a direcot
Hello everybody,
hg and svn packages do set vcs revision infos for package versions. Any
reason this does not apply to git, cvs and darcs?
Using a date string has the drawback that two revisions compiled the same day
result in packages with the same version...
A patch for git is attached. Any ch
On 17/07/12 19:41, Christian Hesse wrote:
> Hello everybody,
>
> hg and svn packages do set vcs revision infos for package versions. Any
> reason this does not apply to git, cvs and darcs?
>
> Using a date string has the drawback that two revisions compiled the same day
> result in packages with
Allan McRae on Tue, 2012/07/17 20:00:
> On 17/07/12 19:41, Christian Hesse wrote:
> > Hello everybody,
> >
> > hg and svn packages do set vcs revision infos for package versions. Any
> > reason this does not apply to git, cvs and darcs?
> >
> > Using a date string has the drawback that two revis
It turns out when you set the filelist for a package to include
"usr/lib/foo" in the pactest suite, it thinks there is only the
file "usr/lib/foo" in there... No "usr/" or "usr/lib/" directory.
This makes life difficult when testing code that scrolls through
a filelist looking for directory entrie
Make files_msort available to the library as sorting a filelist will
be useful for packages where the filelist changes after resolving symlinks.
Signed-off-by: Allan McRae
---
lib/libalpm/be_package.c | 49 +---
lib/libalpm/package.c| 48 ++
File paths are resolved if necessary during inter-package conflict
checks so that packages carrying the same effective file due to
directory symlinks on the filesystem are flagged as conflicting.
Signed-off-by: Allan McRae
---
Prepare for some ugly...
lib/libalpm/conflict.c | 180
This applies to a case such as when /lib is a symlink to /usr/lib. If a
package is installed which contains /lib/libfoo.so, pacman will complain
if this package is then "fixed" to contain /usr/lib/libfoo.so. Since
these have the same effective path and it exists within the same
package, ignore the
On 18/07/12 00:42, Allan McRae wrote:
> File paths are resolved if necessary during inter-package conflict
> checks so that packages carrying the same effective file due to
> directory symlinks on the filesystem are flagged as conflicting.
>
> Signed-off-by: Allan McRae
> ---
>
> Prepare for som
12 matches
Mail list logo
